I have a DB2 datasource and while mapping Appian datastore entities to the

ankitt over 9 years ago

I have a DB2 datasource and while mapping Appian datastore entities to the existing DB2 tables I am getting this error:
"The data source schema does not match the type mappings: Wrong column type in DB2ADMIN.EMPTABLE for column EMP_NUMBER. Found: char, expected: nvarchar(255) (APNX-2-4056-000)"

In my CDT there is a field "EMP_NUMBER" of type "Text" which I am trying to map to a column "EMP_NUMBER" of type "nvarchar"
In Appian we have only "Text" for all string type fields.
Is there any solution to this problem? ...

Discussion posts and replies are publicly visible

0 Aleksi White
Appian Employee
over 9 years ago

Could you attach the XSD for that CDT?
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 venkateswarai917 over 9 years ago

i think, the database column type should be nvarchar(length)/vchar(lenght) - it supports unicode characters, if you application requires to have the unicode chars to save, you can use it and char if fixed length may not work in all the time, because your text may not store correctly. so better you can change the column type is database as vcahar(length) / nvarchar(length).
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Eduardo Fuentes
Appian Employee
over 9 years ago

In order to make your data store to map correctly to your table you need to add the @Column(name="" columnDefinition="") annotation to specify the expected column name and type. For example

<xsd:element name="EMP_NUMBER" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="appian.jpa">
@Column(name="EMP_NUMBER" columnDefinition="nvarchar(255)")
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 pattye over 9 years ago

Not sure if this question was ever answered, but I'm having the same issue trying to map an Oracle char column, I get the "Wrong column type" error. Attached is the excerpt from my XSD file for the char column, and the resulting error. I am following the instructions for "Matching a CDT to an Existing Table Schema" here, forum.appian.com/.../Defining_a_Custom_Data_Type.html, where the specific example uses CHAR.
Data Type Mappings Error.docx
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Eduardo Fuentes
Appian Employee
over 9 years ago

The issue is you have two @Column annotations. This is not supported:

@Column(name="VALID_CREDENTIALS" columnDefinition="CHAR(1) NOT NULL")
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Eduardo Fuentes
Appian Employee
over 9 years ago

<xsd:element name="ValidCredentials" type="xsd:string">
          <xsd:annotation>
                    <xsd:appinfo source="appian.jpa">
                              @Column(name="VALID_CREDENTIALS" columnDefinition="CHAR(1) NOT NULL")
                    </xsd:appinfo>
          </xsd:annotation>
</xsd:element>
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 pattye over 9 years ago

Putting it on one line worked, thanks. The reason I had two @Column annotations is because that is how we did it in the Advanced Data course. I'm looking in the Advanced Data Manual -7.6.pdf, and it has the two @Column annotations in several examples, so you may want to pass this along to the training folks. It actually has been working for me, just not in the case of the CHAR.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel