In many cases, we have to do join other than primary key for the tables as same can't be configured with sync Record type and ultimately, we need to depend on Database views and we loose many capabilities of Sync Record type
Discussion posts and replies are publicly visible
I think that you can already use custom record fields for relationships.
docs.appian.com/.../record-type-relationships.html
Record relationships are there as a compliment to the joins between multiple records. And using relationships much of the features of views are replicable.
Did you ever figure out how to do this? Stefan's answer didn't help me much.
Create a sync-time custom record field on each side and define it as unique.
How do we create a unique sync-time custom record field? The question is imagine I have CASE table with 2 columns TRANSACTION_ID and ROLE_ID (primary key id CASE_ID). Imagine I have another table that doesn't have CASE_ID as a reference but it has TRANSACTION_ID and ROLE_ID (primary key as SKILL_ID). How do I join these 2 on TRANSACTION_ID and ROLE_ID?
erickp0002 said:How do we create a unique sync-time custom record field?
What is your question here? I mean this is a pretty basic operation ...
You can join with one column, say transaction id using add relationship option in claim record. After clicking on add relationship Select the skill record and then map relationship using one of the transaction id column.