how to control global variable reference while printing multiple customer's information? - livecycle

i have multiple customers information in a xml file while previewing that xml in Adobe LiveCycle Designer in all pages it was showing global variable reference ,i want to see each customer information in separate page.
Ex: i have 3 customers information in a xml file and customer name is a global variable
1.a
2.b
3.c
while previewing the xml in xdp template customer name is over riding in all pages that is customer "a".
can any one plz help on this.

Related

CSV File upload where columns are automatically mapped to database

I am trying to automate a process where a team member is given a csv list with columns dealing with First names, last names, email addresses, addresses, phone numbers, and several other columns that are unique to each customer from a customer and then they have to upload the csv file into our system. For example, some customers could send a file with only first name, last name, and email addresses, while the next customer could send a file with those three along with certain ID columns that are directly valuable to them and them only.
The issue is each customer has different names for their columns than we have in our database, so the user has to manually map their columns to our columns in the database through a dropdown menu.
As you can see below, the name on their file upload could be "first_name" and it would match directly with our db column of "first_name". However some customers could have "f_name" or "first name" and we would have to map it directly in the drop down to the "first_name" column in our database.
Unfortunately these docs comes from the customer and we cannot automate it to have one csv document that everyone uses with the same exact columns. Is there a way to not have to map those manually and have that entered into the database automatically into the correct columns?
file upload

Google Data Studio: Filter report data through parameter in URL

I have a Google sheet where each row contains data for a single person.
First column is an alphanumeric random id.
Is there any way I can build a personal score card report which I can share with each person through a link?
The link would contain a parameter for filtering the datasource by the id column. I mean sharing by sending links via email, for example:
Send an email to John with the following link: <url>?id=kfdjfhdfljdshfsdkj
Send an email to Mark with the following link: <url>?id=fdyfdhfsfjsdkjfksd ….
I have thought about adding a filter control plus enabling bookmark urls, but would like to avoid that as that would be a possible security breach. Other ideas?
Thanks
If you can put your data in BigQuery, an alternative approach is to use authorised views. It is explained in details in How To Control Access To BigQuery At Row Level With Groups
The filter based on the email address feature can be implemented by adding an email address field alongside the existing field(s), such as alphanumeric random id in the Google Sheet.
Once that's done, connect the Google Sheets Data Source to Google Data Studio, and then at the Data Source, filter based on the email address of the respective user ID (filter located on the upper left of the Data Source section).

Relational mapping of files and entities in the database

i'm working on a new project and looking into a good approach/ Best practise for file storage and how to efficiently map the files to several resources in a relational data model.
Note: All files are uploaded on a filesystem (not a database)
Option 1
Creating a Files table to store meta data of each file and create a relation with each resource (e.g. user_files, product_files, ... )
Questions: Will all files be stored in a single table? If I want to fetch the user avatar I have to search in a table that also contains product images or pdf documents?
Option 2
Store the needed file meta data with each resource.
Downside: each resource can only have 1 image. (good for user avatar?)
Option 3
Files are created using a hash of the resource (e.g. user_1243_avatar)
No relation will be stored and the url will be build when the resource is fetched.
Are there other options to consider?
all input is welcome.
It's good that you store files in the filesystem. I used option 1 in a recent project and would recommend it.
If I want to fetch the user avatar I have to search in a table that also contains product images or pdf documents?
You make it sound as if you'll have to do a table scan. In my DB, a user's avatar was indicated by an avatar_file_id in the users table, so I could join from users to files directly using an index.
Your user_files sounds too generic. Users could have different files for different purposes, are you just going to lump them all together? Would you create a table person_to_person to lump together friends, marriages, manager/employee, parent/child, etc? I wouldn't.
Create different tables for different purposes, e.g. a one-to-one table user_avatar (or denormalize it into your users table). Some more examples might be product_images, product_specs, product_helpfiles, etc.

relations variable of content-type drupal 7

I have created a content type called Customer.
I am creating other content called reports.
A customer has several reports.
How could create a variable in the content-type reports relations with the customer's name on content-type customer?
thanks
You should use Drupal Entity Reference module. Download, install and enable it, and then, you have to add a new field in content type "Reports", namely customer, of type "Entity reference" (this field type was added by Entity Reference module). Once you have added this field, you have to choose which kind of nodes can be referenced. Select Customer in the checkbox list.
You can also choose the way you want to determine which customer owns a report. You have several options: selection checkboxes, autocomplete field, etc. Take a second to determine if a Report should be linked to one or more customers. In case it must be linked to a single customer, make sure to limit the number of fields to one.
Using this module you will not only link the customer's name to the report, but you will also link the whole entity. You will be able to display the customer name as a link to the customer node.

drupal 7 Displaying data from different content type in single row in views using relationships

I have a Taxonomies like group , category hobbies, CV and i have a 3 content types.
1st content type is Company which has a field project code , then it has field called CV which is of type term reference to Taxonomies CV.
There is a field called group and category which are both term reference of to taxonomy group and category
Similarly i have field called RM which is entity reference of type User and account manager which is also a entity reference of type user.
Another Content type called CXO which has fields name , number, and Hobbies which is a term reference to Taxonomy hobbies.
In This we have a field company which is entity reference of content type company created above so this person belongs to one among companies.
Last Content type is Coordinator which also has all same fields as CXO and it also has hobbies as term reference. Similarly as CXO we also have a field company which is entity reference of content type company.
So i wanted to view all the fields together in one table.
Like Project code, company , CV , category , Group , RM , Name from CXO , Number from CXO , Hobby from CXO , Name from Coordinator , Number and Hobbies of Coordinator.
ALl these data i wanted to be come in a single row, like one project will have all these details.
Please help me with this, i think something i have to do with relationships, Can somebody help me with this.?
In order to gain access to the fields of other content types you should add in the relationships area the appropriate entity reference field.
For example if you want to make available in a companies view all the CXOs you should add in relationships the referencing entity "A bridge to the Content entity that is referenced via field company" .
Due to many many relationships at your case you 'll end up with many duplicates so I 'd suggest to use the distinct setting under "query settings" or a "group by" in aggregation settings.

Resources