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
+1
person also asked this
people also asked this
Replies
10 replies
Subscribers
10 subscribers
Views
7432 views
Users
0 members are here
Share
More
Cancel
Related Discussions
Home
»
Discussions
»
General
I created a view that includes a calculated field which came in with a type '
judym598
Certified Senior Developer
over 9 years ago
I created a view that includes a calculated field which came in with a type 'bigint(21)' that I can't seem to change. I'm trying to create a data type for this view but I can't seem to get it mapped correctly. I tried to make this field a 'bigint' in the xsd file using the jpa notation. I can create the data type but when I add it to the data store and try verifying the mapping, I get this error:
A type mapping annotation is invalid: identifier mapping has wrong number of columns: IPSActiveUsersVDT2506 type: integer (MappingException) (APNX-2-4055-000)
Here's my xsd file (note: I tried deleting the first jpa notation associated with the 'id' and also tried to remove the primary key on 'nbrActiveTeams' in the data type since that's not a primary key but so far nothing's helped.
<xsd:schema xmlns:xsd="
www.w3.org/.../XMLSchema"
xmlns:tns="urn:com:appian:types" targetNamespace="urn:com:appian:types">
<xsd:complexType name="IPS_ActiveUser...
OriginalPostID-168979
OriginalPostID-168979
Discussion posts and replies are publicly visible
Parents
0
PhilB
A Score Level 1
over 9 years ago
I see you've resolved your issue but you might find the below of interest.
MySQL will generally return calculated integer fields in a view as bigint. You can work around this by creating a function in MySQL that takes an input of bigint and returns an integer type, and then call that function for the relevant fields in the view's select.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
Reply
0
PhilB
A Score Level 1
over 9 years ago
I see you've resolved your issue but you might find the below of interest.
MySQL will generally return calculated integer fields in a view as bigint. You can work around this by creating a function in MySQL that takes an input of bigint and returns an integer type, and then call that function for the relevant fields in the view's select.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
Children
No Data