Hello All,
We observed one issue
1. Parent CDT -> one of the columns type is document
2. We updated the child CDT (added a new column) upon updating the child CDT, the parent CDT filed type changed from document to anytype.
Did anyone face the same issue?
Discussion posts and replies are publicly visible
I do not really understand.
In the parent there is a field of type document. Then there is some, probably nested, child CDT.
What do you mean with "added a new column"? Is this about a new field?
Where do you see this behaviour? Do you have some code you can share?
Hello
1. Parent CDT with document field and child CDT.
2.
2.1 Child CDT before the update
2.2 Added new field in the CDT
3. After Step 2.2 parent CDT's fields type changed from document to number
Thank You,
Sneha.
The data type "document" does only exist inside Appian. If you modify it outside of Appian, it will turn into an integer as this is the underlying representation.
I consider this to be expected behaviour.
BTW, I recommend to manage the data structures only in CDTs and let Appian maintain the DB schema. I think this fits the low-code spirit of Appian way better than hand crafted XSDs or SQL scripts.
Parent CDT is transient CDT ( not added to any data store/ CDT is not mapped any table in DB).
In this case, is it expected that parent CDT data types that exist only in Appian get changed to number/ any type ?
Sorry, I didn't understand "I recommend to manage the data structures only in CDTs and let Appian maintain the DB schema", can you please explain with an example?
Unknown said:If you modify it outside of Appian
This user is not saying they're modifying the CDT outside of Appian, though.
Sneha Yada, I just reproduced the described behavior in my TEST environment using 2 brand new CDTs (parent and child, similar to the ones you pictured). The Parent CDT has 2 separate fields of Document type, and after simply adding a new field to the Child CDT, the data type of the Document field in the Parent had changed itself to "Integer" instead.
This is definitely a bug. I recommend you open a Support Case with Appian - this is something they'll need to address.
Edit to add: I can also reproduce the behavior just by *minorly renaming* one of the fields in the Child CDT. As in, I didn't even have to add a *new* field to demonstrate the breakage.
Thank You Mike for your response, we will raise a support case for this.
Yes, we will be able to replicate the issue by making (adding a new field/renaming existing field/ change filed specifications etc) any changes to child cdt.
I was just testing this on 22.2 but cannot reproduce it. My document type field stays a document.
But I support Mikes recommendation of opening a support case.
Thank you for checking it.
We are using 21.2 and the issue exists in this version.
I just reproduced it on my 22.2 environment. In my child CDT the only change I needed to make was addition of a single character to the end of one of the field names.
Before:
After:
Sneha Yada - can you confirm whether or not you raised a support case for this already?