Appian Community
Site
Search
Sign In/Register
Site
Search
User
DISCUSS
LEARN
SUCCESS
SUPPORT
Documentation
AppMarket
More
Cancel
I'm looking for ...
State
Not Answered
Replies
4 replies
Subscribers
7 subscribers
Views
2010 views
Users
0 members are here
Share
More
Cancel
Related Discussions
Home
»
Discussions
»
Administration
My application package has a process model having a "Call a Web Service&quo
simranjits
over 10 years ago
My application package has a process model having a "Call a Web Service" ss and also the cdt generated by the process model. When I inspected it on the test server, it threw an error:
An error occurred while importing the XSD. No types have been imported. Details: Invalid Type: Type Error: Qualified name not unique or temporary - .........(APNX-1-4050-000) (APNX-1-4071-007)
This error as per me could be because of the following:
1. The presence of both, the web service call and the respective cdt generated as a result of the web service call. But best practices suggests to include both in the package, so no problem here.
2. The cdt has a reference to Appian reserved namespace: <xsd:appinfo source="
www.appian.com/.../2009">
, not in the xsd namespace, but somewhere else in the xsd. But now when I have simulated the issue by importing only the xsd with the reserved namespace, it gets imported whithout any error. So even the...
OriginalPostID-126131
OriginalPostID-126131
Discussion posts and replies are publicly visible
Parents
0
Eduardo Fuentes
Appian Employee
over 10 years ago
Internally I can confirm the root cause is the same. Even inspection will try to resolve dependencies between CDTs which can result in this behavior. In summary the issue is the use of the enumerations as explained in that post.
This impacts both CDTs coming from Web Services and from XSDs
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
Reply
0
Eduardo Fuentes
Appian Employee
over 10 years ago
Internally I can confirm the root cause is the same. Even inspection will try to resolve dependencies between CDTs which can result in this behavior. In summary the issue is the use of the enumerations as explained in that post.
This impacts both CDTs coming from Web Services and from XSDs
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
Children
No Data