Difference between un synced record type and query entity

aswin26 Records are new appian way of accessing the data from database as well as forming relations (view), whereas for achieving the same thing using cdt method you would need to create a seperate view and create a seperate cdt object for that view.

Also records can have relation with other system objects like entity(tables) residing in Salesforce

Thanks amiteshsin. In my use case i tried synced records and establised the realtionship instead of view, but it was not accepted. So I had to create a view and then i created a record type for that view.

I just want to understand if my way of creating a record type for a view and then displaying it in a table is better or should I directly get the data from the view using queryEntity().

Is there any performance difference between these two?

Yes you can use entities instead of records but you'd be missing out on one of the most powerful features: relations where you can bring in data from other sources and make relationships with the data stored in your application. Relations should also simplify the way you manage data within your application.

docs.appian.com/.../Record_Type_Object.html

Thanks Mathieu Drouin. I dont have my data from multiple sources. My main concern was i need to establish "LEFT JOIN" between the tables. I was not able to perform the left join in records, so i opted for views

f you have a Record against a view, it will have to be unsynced so I don't think there should be much of a difference performance wise.

Interesting. Perhaps you could have had 2 synced record types but the relationship would have had to be done via queries rather than relationships?

Can you please elaborate on how we establish relationship using queries?

record relation is based on type of relation and you can pull corrsponding value from related record for the same key and still show all the rows from main record. It should give same output as left join. Isn't?