• State Not Answered
  • Replies 5 replies
  • Subscribers 5 subscribers
  • Views 1967 views
  • Users 0 members are here
Related Discussions
Home » Discussions » Integrations

#CDT #EXPORT We are experiencing an export issue for several CDTs. T

felixl973
#CDT #EXPORT We are experiencing an export issue for several CDTs.

The message that we get is the data for datatype [id=3430 uuid={http://www.407etr.com/ea/soa/asset/ds/tm/tl/transponder}identifyDuplicatesResponse] could not be retrieved for export. Cause: java.lang.NullPointerException (APNX-1-4071-002)

Attached is the debug and error logs for this specific CDT export error. We are experiencing several CDTs with this issue.

We have tried to download the XSD, but we are unable to download the XSD through Appian. When we click the download xsd button we get the following message "A server error was encountered while processing your request. Please try again."

These CDTs originated as Web Service Import. I believe these were first introduced when we were using Appian 6.6. Now we are using Appian 7.4.

When we refresh the web service we get the following warnings in the Call Web Service set-up:
The following warnings indicate potential issues with th...

Export CDT Error Log 20140317.txt

OriginalPostID-104067

OriginalPostID-104067

  Discussion posts and replies are publicly visible

Parents
  • 0
    Appian Employee
    1. www.ibm.com/.../
    2. Now, in terms of how this looks in Appian in the Primary Data Source, well, the problematic CDTs in your DT_MODEL table will have in their XMODEL (transformed model) column the following inside its definition:

    <details key="namespace" value="Response"/>

    instead

    <details key="namespace" value="##targetNamespace"/>

    Here's an example (excerpt) from the XMODEL table of a CDT that won't be able to be imported (and is not needed for export since you can use the approach I suggested above)

    <eAnnotations source="http:///org/eclipse/emf/ecore/util/ExtendedMetaData">
    <details key="kind" value="element"/>
    <details key="name" value="Prospect"/>
    <details key="namespace" value="Response"/>
    </eAnnotations>


    while this is the excerpt of the one that works

    <eAnnotations source="http:///org/eclipse/emf/ecore/util/ExtendedMetaData">
    <details key="kind" value="element"/>
    <details key="name" value="ResponseProspect"/>
    <details key="namespace" value="##targetNamespace"/>
    </eAnnotations>
Reply
  • 0
    Appian Employee
    1. www.ibm.com/.../
    2. Now, in terms of how this looks in Appian in the Primary Data Source, well, the problematic CDTs in your DT_MODEL table will have in their XMODEL (transformed model) column the following inside its definition:

    <details key="namespace" value="Response"/>

    instead

    <details key="namespace" value="##targetNamespace"/>

    Here's an example (excerpt) from the XMODEL table of a CDT that won't be able to be imported (and is not needed for export since you can use the approach I suggested above)

    <eAnnotations source="http:///org/eclipse/emf/ecore/util/ExtendedMetaData">
    <details key="kind" value="element"/>
    <details key="name" value="Prospect"/>
    <details key="namespace" value="Response"/>
    </eAnnotations>


    while this is the excerpt of the one that works

    <eAnnotations source="http:///org/eclipse/emf/ecore/util/ExtendedMetaData">
    <details key="kind" value="element"/>
    <details key="name" value="ResponseProspect"/>
    <details key="namespace" value="##targetNamespace"/>
    </eAnnotations>
Children
No Data
© 2024 Appian. All rights reserved.
We want to hear from you! Submit a review on Gartner or G2.