CDT became invalid after modifying its precedent CDT

RE: CDT became invalid after modifying its precedent CDT

Amey Dusad — Thu, 29 Apr 2021 17:10:44 GMT

I am also facing the same issue. I have just changed fields in cloud database and after that updated CDT with respect to changes in databse. Suddenly my CDT became read only. How to resolve it??

RE: CDT became invalid after modifying its precedent CDT

Peter Lewis — Tue, 16 Mar 2021 18:11:55 GMT

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.

RE: CDT became invalid after modifying its precedent CDT

Harshit Bumb (Appyzie) — Tue, 16 Mar 2021 17:57:51 GMT

Yes, I did. Attaching the code below.

<?xml version="1.0" encoding="UTF-8"?>
<xsd:schema targetNamespace="urn:com:appian:types:VP"
  xmlns:tns="urn:com:appian:types:VP" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
  <xsd:complexType name="VP_createProducts">
    <xsd:annotation>
      <xsd:appinfo source="http://www.appian.com/ae/types/2009">
        <ns2:Metadata xmlns:ns2="http://www.appian.com/ae/types/2009">
          <ns2:versionUuid>0001e60d-7f4b-8000-fcd4-7f0000014e7a</ns2:versionUuid>
          <ns2:history>
            <ns2:historyInfo versionUuid="0001e60d-7f4b-8000-fcd4-7f0000014e7a"/>
          </ns2:history>
        </ns2:Metadata>
      </xsd:appinfo>
    </xsd:annotation>
    <xsd:complexContent>
      <xsd:extension base="xsd:anySimpleType"/>
    </xsd:complexContent>
  </xsd:complexType>
</xsd:schema>

RE: CDT became invalid after modifying its precedent CDT

Peter Lewis — Tue, 16 Mar 2021 15:41:40 GMT

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.