Issue creating relationship between two records in Appian

Certified Associate Developer

Hello,

I'm trying to create a relationship between two records in Appian. In the database, I have already defined the primary keys, foreign keys, and constraints correctly.

However, when I go to the record type view to create the relationship and select the field from the table that contains the foreign key, I’m unable to select any field from the related record. The primary key field does not appear as an available option.

Could you please advise on what might be causing this issue?

Thank you.

  Discussion posts and replies are publicly visible

Parents
  • 0
    Certified Lead Developer

    Is this a 1:many relationship or many:1 relationship? Depending on which of your records you start on, this would be inverted and thus your FK field wouldn't show up where you expect it to.

    Aside from that, we would probably need more information about your records (via screenshots of the relationship screen) to help.

    As a side note, Appian records do not need a formal database foreign key in order to create a relationship between two sync'ed record types. We can infer that FK's are not necessary because the data fabric is designed to stitch data together across many databases, where one database has no schema information about the others and therefore no FK can exist at the database level. It is a GOOD practice to keep FK's and record relationships in sync with each other where possible, but not a functional requirement of sync'ed records.

Reply
  • 0
    Certified Lead Developer

    Is this a 1:many relationship or many:1 relationship? Depending on which of your records you start on, this would be inverted and thus your FK field wouldn't show up where you expect it to.

    Aside from that, we would probably need more information about your records (via screenshots of the relationship screen) to help.

    As a side note, Appian records do not need a formal database foreign key in order to create a relationship between two sync'ed record types. We can infer that FK's are not necessary because the data fabric is designed to stitch data together across many databases, where one database has no schema information about the others and therefore no FK can exist at the database level. It is a GOOD practice to keep FK's and record relationships in sync with each other where possible, but not a functional requirement of sync'ed records.

Children
No Data