• State Verified Answer
  • Replies 14 replies
  • Answers 1 answer
  • Subscribers 12 subscribers
  • Views 10254 views
  • Users 0 members are here
Related Discussions
Home » Discussions » Data and Records

Changes to CDT are discarded upon saving the CDT when CDT contains field of type Document

Morné Lombard
A Score Level 1

Hi all, I have a strange issue where the changes I make to a CDT that has a field of type Document, are not saved when I click Save

Upon clicking Save, the ID is no longer the Primary Key and the length of the text field disappears (after I have set the primary key and the field length).

I have also tried to import from an XSD where the fields are defined correctly, but after import, the changes are gone again.

I only have this issue when the CDT has a field of type Document in it.

Can anyone explain to me why this is happening, and provide a possible solution?

The only solution I can think of is to change the type from Document to Number (Integer) and just save the document ID in the field.

When I remove the field of type Document, it works fine and the changes are kept and saved.

 

Thank you,

Morné

  Discussion posts and replies are publicly visible

Parents
  • 0
    A Score Level 2
    Hi Morne, I wonder how u had a Document type in a CDT, Since the CDT Field types can be from Primitive or other CDT. I think that Document is of type CDT. We generally have the documentId of type Integer which holds the Appian Doc id.

    for more info please refer docs.appian.com/.../Custom_Data_Types.html
    In the properties they mentioned.
    Field Types Fields can be of the following types: primitive, custom. Other Appian types are not available.
  • 0
    A Score Level 1
     in reply to chandu

    Hi Chandu, I am not sure if it is a Primitive Data Type or not, because I see the namespace is an Appian namespace, as seen in the screenshot below, which is the same namespace as the Text and Number (Integer) Primitive Data Types:

    Maybe this is a new 18.2 object?

     

    Not sure if this helps, but in the XSD, it looks like this: (notice the type attribute is a:CollaborationDocument)

    <xsd:element form="unqualified" name="item" nillable="true" type="a:CollaborationDocument" />

     

    Thanks,

    Morné

Reply
  • 0
    A Score Level 1
     in reply to chandu

    Hi Chandu, I am not sure if it is a Primitive Data Type or not, because I see the namespace is an Appian namespace, as seen in the screenshot below, which is the same namespace as the Text and Number (Integer) Primitive Data Types:

    Maybe this is a new 18.2 object?

     

    Not sure if this helps, but in the XSD, it looks like this: (notice the type attribute is a:CollaborationDocument)

    <xsd:element form="unqualified" name="item" nillable="true" type="a:CollaborationDocument" />

     

    Thanks,

    Morné

Children
No Data
© 2024 Appian. All rights reserved.
We want to hear from you! Submit a review on Gartner or G2.