nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Data Deploy

Sathishbsl

Hi,

I am using TS6.5 and NT env.
I have a DCR where the form fields will be dynamically changing according to the selection of an item in combo box. For example, I have a combo box with two values say A and B. If the user selects A, he will see 3 text fields and for B, there are 3 text fields and a combo box. The XML structure will be different for both the cases. We can't go with two dcrs. Here we need to perform Data Deployment for these xml files which will be stored in the data folder. In the ddconfig.xml file, can we have two main groups(One group will deploy content to X table and another will deploy to Y table)? if so, can we deploy the single group according to the condition selected by the user(A or

.

Please let me know if you need further details on the same.
Your help on this is highly appreciated.

Thanks in advance.
Sathish E

Find more posts tagged with

Comments

gzevin

Both cases represent the same DCR, so why can't you have all the fields in the table? Similar to a DCR, some tags (fields) will be empty

Sathishbsl

Hi Greg,

Thanks for ur feedback. We can't keep all the fields in the same table.. It should be splitted to the two tables with reference to the item selected in the combobox. Can I read the the DCR(XML files) before deploying and substitute the dbshema tag according to the item selected? If so, will it be good if I keep all the fields in a single dcr with all non mandatory items provided the validations will be performed in the DCT.

Please let me know if I am going in the wrong path..
Sathish

Bill Klish

The logic if combo box value A, deploy to table 1, if value is B deploy to table 2 is not possible in a DataDeploy configuration file.

If for example you are deploying one DCR at a time via a workflow that triggers this deployment, you could have 2 definitions in your ddconfig file and then have an upstream process (external task, etc.) that figures out which of the 2 deployment configurations to call, and then calls datadeploy with the definition for the correct table.