Type mapping annotation is invalid: Repeated column in mapping for entity

There might be a copy paste problem in XSD, the error is clearly stating that "tcfhsmsrsnplcfrvltngcstmrnd" has been mapped twice. You can just check with the help of ctrl+f to find the repeated mapping for that column.

if you still want to map the two cdt fields for the same column you need to mention as Insertable="false" and updatable="false".
If you still cannot to figure it out, please attach the XSD we will try to help you.

Hi Chandu, thanks for your reply. I do not know where the column "tcfhsmsrsnplcfrvltngcstmrnd" is inside my XSD, I am not sure where Appian gets that name from.

You can download my XSD using the following link.
expirebox.com/.../a237161edac0d5ed0703e7347fb3b588.html

Thank you for your assistance.

You have pretty long field names, so Appian tries to map them to the database by stripping vowels and then capping names at 30 characters. I think both tcfHasMeasuresInPlaceForEvaluatingCustomerUnderstanding and tcfHasMeasuresInPlaceForEvaluatingCustomerUnderstandingElaboration are getting mapped to the same name (tcfhsmsrsnplcfrvltngcstmrnd), so Appian complains with that error. You need to manually define a column name @Column(name=...) in your XSD.

Hi Carlos, this is a valid point. I also just found that in Appian's JPA documentation, thank you very much for pointing that out. Must the @Column(name=...) also be less than 27 characters? Or does it not matter when a @Column(name=...) is specified?

Thank you.

You're welcome. In general, I don't think it matters, but do check your DBMS. In particular, Oracle has a hard limit of 32 characters (or something along those lines.)

Ah I see that MySQL has a column name limit of 64 characters. I'm going to add the @Column annotation and shorten the names of the long field names. This should fix it, stay tuned as I will update you once I have done so :)

Ah I see that MySQL has a column name limit of 64 characters. I'm going to add the @Column annotation and shorten the names of the long field names. This should fix it, stay tuned as I will update you once I have done so :)