Appian Community
Site
Search
Sign In/Register
Site
Search
User
DISCUSS
LEARN
SUCCESS
SUPPORT
Documentation
AppMarket
More
Cancel
I'm looking for ...
State
Verified Answer
+1
person also asked this
people also asked this
Replies
16 replies
Subscribers
5 subscribers
Views
6594 views
Users
0 members are here
Share
More
Cancel
Related Discussions
Home
»
Discussions
»
Integrations
I am building XSD where i need to map My -SQL ENUM data type . I tried like be
vineeta6579
over 10 years ago
I am building XSD where i need to map My -SQL ENUM data type . I tried like below but Appian doesn't recognize it as enum type
_______________________________________________
<xsd:element name="car">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:enumeration value="Audi"/>
<xsd:enumeration value="Golf"/>
<xsd:enumeration value="BMW"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
____________________________________________________
Attached: XSD and table structure.....
OriginalPostID-113805
OriginalPostID-113805
Discussion posts and replies are publicly visible
0
vineeta6579
over 10 years ago
After importing xsd have you tried to create data store and published it.. In my case It shows error when I tried to publish.
Yes I am using 7.5
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
Aleksi White
Appian Employee
over 10 years ago
The enum type won't map explicitly to one of the Appian types. This is something we haven't tested before, but it looks like the reason Appian is ignoring the enum and reading this as a string is because there is no equivalent enum type for Appian
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
vineeta6579
over 10 years ago
Yes Appian is not recognizing it and considering it as text only.
Any workaround..
how I can create xsd to map my existing database table. For yours reference I am attaching table structure screenshot again..
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
+1
Aleksi White
Appian Employee
over 10 years ago
The structure in the XSD will map to a CDT. The CDT structure has no way of supporting an enumerated class, so it can't map to a DB table with an enum. Looking at the custom data type documentation, there is no mapping for an enum, so this won't be possible.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Reject Answer
Cancel
0
vineeta6579
over 10 years ago
May be .. But in documentation they have mentioned about @Enumerated JPA annotation but Havant provided any sample!!!
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
Aleksi White
Appian Employee
over 10 years ago
It is not mentioned explicitly, but enumerations and other facets of a type defined in XSD are ignored when converting that XSD to a custom data type in Appian. If the data type cannot be mapped to an existing system or custom data type, the element is converted to a string.
The reason behind this exclusion is relating to the display and validation of your custom data. Appian can not account for the infinte possibilities of validating against enumerated data or the possibility of having to develop a display in the interface for each. This does seem like something that should be clarified in the documentation.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
<