Updated CDT error

judym598

Certified Senior Developer

over 7 years ago

I was recently updating a data type and when Appian validated it with the data store, I got the following error, "The data source schema does not match the type mappings: Wrong column type in Appian.pshactiveagreementsdetail_v for column urlfordocuments. Found: text, expected: varchar(255)"
This data store contains data types associated with views. I recently changed the size of one of the fields in the original table used in this view from a varchar(450) to varchar(1000). The table still shows it as varchar but the view shows it as 'text'. Since the type I selected for this field in the CDT is 'Text', why am I getting this error? Why is it showing up as text in my view vs a varchar type? I'm guessing because of the size. Can I safely change the type in my table to 'text'? I have several tables that have fields with a varchar type > 255. Is that a problem? I need this view in order to display data from multip...

Discussion posts and replies are publicly visible

Parents

0 judym598
Certified Senior Developer
over 7 years ago

This field is not part of an index. I'm guessing if I don't want to change the type in the table to 'text(1000)', I could add the @Column notation like this:
<xsd:element name="renewalStatus" nillable="true" type="xsd:string" />
<xsd:annotation>
<xsd:appinfo source="appian.jpa">
@Column(columnDefinition="TEXT")
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
Does this make sense? (see attached)
Colton - If I did as you suggested, I would have to cast it as 'char(1000)' to match the table definition, right?
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Reply

0 judym598
Certified Senior Developer
over 7 years ago

This field is not part of an index. I'm guessing if I don't want to change the type in the table to 'text(1000)', I could add the @Column notation like this:
<xsd:element name="renewalStatus" nillable="true" type="xsd:string" />
<xsd:annotation>
<xsd:appinfo source="appian.jpa">
@Column(columnDefinition="TEXT")
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
Does this make sense? (see attached)
Colton - If I did as you suggested, I would have to cast it as 'char(1000)' to match the table definition, right?
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Children

No Data