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; } } }

Avoiding unwanted extra recrods in DD

vinitsmore

Hi

In datacapture.cfg, I have a container which containes another 4 containers as below
1) Text Widget
2) Image Widget
3) Attachment Widget
4) URL Widget.

User can select one of the above options at a time, and as per user's choice, that container will be displayed..

Tab is Object_Details
Container - object_desc_container

DD file, is configured as below
1) Text Widget information is stored into Mon_TextWidget table.
2) Image widget - Mon_ImageWidget
3) Attachment - Mon_Link_Attachment
4) URL - Mon_Link_URL

Now the problem is, If DCR has 1 Text and 1 Image widget, it also deploys data in Mon_Link_URL and Mon_Link_Attachment table, with null values for attachment and url widgets.

That's how our DD is configured.

Is there any better way to configure the DD file . Please suggest. Here I am attaching the datacapture.cfg file and DD file for reference.

Thanks
Vinit

Find more posts tagged with

Comments

vpatel

I haven't looked at your DCT and DD configs but it sounds like that your DCR may have hidden fields with no-value (null/space) or some default values for the fields that getting deployed even though you are not expecting that.

vinitsmore

Yes.. You are right..

I have some fields with null / empty values.. I want to avoid deployments for these fields..

Is it Possible by any chance

Thanks
Vinit

thatfish

If your requirement is to not to deploy if a field is empty I think the simple answer is no. This would require logic in the _dd file.

The _dd cfg files are one-to-one mapping files from the database to a DCR. Logic cannot be placed in these files.

Atleast this my understanding.

Where does the requirement come from ?

vpatel

Yes.. You are right..

I have some fields with null / empty values.. I want to avoid deployments for these fields..

Is it Possible by any chance

Thanks
Vinit

Remove those hidden empty containers / fields from the DCR itself...If that's not an option you'll have to explore other possibilities.

vinitsmore

If your requirement is to not to deploy if a field is empty I think the simple answer is no. This would require logic in the _dd file.

The _dd cfg files are one-to-one mapping files from the database to a DCR. Logic cannot be placed in these files.

Atleast this my understanding.

Where does the requirement come from ?

----------------------------------------------------------

Thanks for the clarification. I would like to explain you in more detail

I have a container in Datacapture.cfg file.. which contains.. 4 containers..as
Text, Image, URL and Attachment.

I have 4 groups in DD for storing data in seperate tables for Text, Image, Attachment and URL.

Now, if user selects only Text Widget, blank data gets inserted into Image, Attachment and URL tables. There are seperate groups ..

If all fields are belong to a single group, then there is option. Data deploy will happen in any case..

Since all there fields are not from single group.. We are trying to avoid data deploy in these tables

Thanks & Regards,
Vinit

vinitsmore

Remove those hidden empty containers / fields from the DCR itself...If that's not an option you'll have to explore other possibilities.

Removing hidden / empty fields from DCR would work.. but its not an option for us..

What could be the other possibilities?

vpatel

Removing hidden / empty fields from DCR would work.. but its not an option for us..

What could be the other possibilities?

If you are the person who's assigned to do this then you'll have to figure out what other possibilities would fit into your environment. Smiley Very Happy

Adam Stoller

I don't know if it will work the way you want, but you might be able to use DD's filters to prevent empty data being deployed. Alternatively, drop DD altogether and write your own DB interface using Perl, Java, or the language of your choice. While it obviously requires more work up-front to do so, it does provide for more control over what does / does not happen.

thatfish

alternatively manage it on the database side e.g. Stored Proc

Migrateduser

It appears that the original poster is leaving out the fact that the top level container is a combination "or" replicant where they can then choose which type of container to add when they click the + symbol. Since DD doesn't understand these types of containers except in the fashion it is functioning, the only option (outside of abandoning DD and writing your own custom DB interface) is to create a custom SP which DD deploys to. This stored procedure would then decide whether to actually create the records in question or not. I suppose it might be possible to deploy to XML files, then clean the XML files and deploy the XML files to the database but this seems like trying to fix a leak with a Machine Gun to me.

If I was doing this I would just let DD deploy blank records to the child tables and then write a view that displayed the data sans the data records with only null values. This is safer than writing your own SP to handle things as DD functions in the default way and only your view of the data is different. It also lets you see the data in its raw form if you ever decide you need to.

Andy