Skip to main content
harshitb6843
March 16, 2021
Question

CDT became invalid after modifying its precedent CDT

  • March 16, 2021
  • 4 replies
  • 0 views

I had a CDT which has a couple of primitive datatype fields and a CDT field. When I changed the child CDT (Added two more fields) then the parent CDT became invalid. Now I am not able to refer to it on any interface using type! and also when I try to open the CDT, it opens in read-only and doesn't show any columns. Also, there isn't any option to download the XSD. I have attached all the supporting screenshots below.

p.s. None of the CDTs were mapped in a DS. Both were being used on the Appian side only. 

4 replies

peter.lewis
Employee
March 16, 2021

That seems weird - are you able to export it in a package / patch? That might at least allow us to see what the current structure of the CDT is.

harshitb6843
March 16, 2021

Yes, I did. Attaching the code below.



  
    
      
        
          0001e60d-7f4b-8000-fcd4-7f0000014e7a
          
            
          
        
      
    
    
      
    
  

peter.lewis
Employee
March 16, 2021

The part that seems strange to me is the section that says <xsd:complexContent>. I'm not certain what caused that to be added, but it's probably the reason you're unable to edit the CDT. Was this a CDT that was created via import of a database table or a plug-in or something? If you have this file you might at least be able to open a support ticket to see if they have seen this before.