Unable to verify 1 to M foreign key relationship for publishing data store

I am on 17.2 and took DB first approach. I have properly named foreign key relationships on the database.

When I try to create a CDT with an attribute referencing parent CDT, foreign key is properly recognized. However, when I  try publish

the data store, the verification process is failing and downloaded script is looking for creating foreign key columns with names

that do not match our naming convention. It needs to be mentioned that the foreign key column has the same name as that

in the database. Why is the verification process is failing?

  Discussion posts and replies are publicly visible

Parents Reply
  • Hi Sudhakar,

    As Justin suggested we may define the foreign key in XSD definition, however since you are in v 17.2, I recommend to use data type designer which is user friendly and provide the exactly same foreign key defined in database in Parent CDT configuration. If not Appian it self creates the foreign key automatically.

    As an example you may refer below CDT's screenshots configuration. Parent CDT: POC_LMS_employeeRecord and Child CDT: POC_LMS_employee_Leave_History with one to Many configuration. If you have foreign key already configured in database tick the check box (I know the name of the column(s) this field should use in the database) and provide the foreign key. If not Appian creates it's own.

    Hope it helps you. Cheers..

Children
No Data