I establish a One-to-One parent-child relationship in Appian by including a reference field for the child Custom Data Type (CDT) within the parent CDT during creation. Although the parent CDT is successfully published in the database, initially, the child lacks a primary key. Appian generates the primary key in the child after publication, associating it as a foreign key in the parent table. However, an issue arises during parent table updates; instead of updating the child table, it consistently creates new records. Recognizing this is likely due to the absence of a primary key in the child CDT, I added the necessary primary key during the update of child table and the child table continues to create new records rather than updating existing ones. Seeking a solution for this behavior.
Discussion posts and replies are publicly visible
just to know whether you are passing primary key id of the records while updating. If you are passing then just provide some screenshots what you have done to better understand the scenario.
Hi Kiran
Thank you for your reply during the updation of data i see that my child primary key was missing so today i sort out my issue
thank you kiran