I have updated a cdt and added an extra column to it. There are few thousands of instances in the old version of the cdt where the extra field is not present. In the process instance as well the cdt is showing in cap sign which means it's referring to the old version. I have done a data migration to populate that extra field for the old instances. However, while writing the data to the table through the process, even though the new column is not present in the old cdt, the database column is getting overwritten by null value.
Is there any way how to avoid this scenario?
Can you try by setting CDT-->Field attribute, nillable =false?
The nillable attribute of an element is retained. When a field with a null value is encountered, the element is not created.
Else need to handle by adding DB constraint.
Sushil Kapoor Thanks for your reply.
I am afraid, if I make the nillable = false, it would behave like a "required" field and it might break if there are any actual null values.
Discussion posts and replies are publicly visible
© 2020 Appian. All rights reserved.