Hi,
I have below Record Type(s) structure.
Now when I try to load the column(s) data in the summary page from the RecordType "D", it is not loading. But, when I ran the "Data Sync" for the recordType "D" manually then I was able to see the data in the
summary page.
FYI: RecordType "B" is having a foreignkey relation ship with column data which is there in the RecordType "B".
Any tips please. Thanks in advanse.
Discussion posts and replies are publicly visible
Can you explain what you mean with "Entity which is storing the data to "B" itself is storing the data to "D". Because, One of the column in "B" is having a Foreign Key relation and an Array to "D"."
Peter Lewis Quick question: The update trigger to a record when writing to DB is based on the table name as defined in the XSD?
Hi Stefan,
Please find the below attached details. Let me know if you need more details for more clarity.
Thanks
I try to sum it up.
You created a CDT B with a nested CDT D. Now you directly write to the table D.
Correct?
Do you need that nesting? I think the idea is to create the CDTs separately and then define the relationships in the records.
Peter Lewis What do you think?
Please find the correct message:
Created a CDT B with a nested CDT D. I am directly writing to B.
So, you write an item to B that includes data stored to D. Now it seems like the record for D is not automatically synced.
I suggest to create a small test case to investigate this matter. If you can reproduce it, open a support case.
Stefan,
More detail can be found in the below link which I am talking about. Thanks.
Appian Community
I would expect that when you write data using nested CDTs (i.e. write to CDT B that contains CDT D) that all data would be written to both tables AND record types that refer to both tables would be synced. To Stefan's question - the update occurs when the table name matches in both the XSD of the CDT and the source of the record type.
The one question I still have - what if you write only to table D (and don't use a nested CDT)? Depending on the answer there, that can help us identify if the issue is that either table D just isn't triggering a sync for any operation or that it is only failing to sync when using a nested CDT.