The main question is about how Appian cache the data when you relate a record type to database tables. Also does this cache mechanism provided when you relate a record type to database views.
Discussion posts and replies are publicly visible
Synced records do not work with DB views. The idea is to make views obsolete with Records.
Synced Record data is stored in the Appian data server which is a no-sql database.
So you mean that every time i refer to the view through the record type, i call directly the database? Ι know that synced record data do not work with db views but i thought that every individual table that called by the view, synced automatically.
A non-synced Appian Record backed by a database view will query that view every time.
Within a evaluation context Appian tries to cache data in case you trigger the same query twice. But this has nothing to do with synced records.
I do not understand what your mean with "i thought that every individual table that called by the view, synced automatically.". Maybe you want to add some details about your use case.
Records are only synced automatically if you use the WriteRecords Smart Service. If you write directly in the database, you need to run a full sync.
Thank you everyone for your answers. I want to take advantage of the cache mechanism when i query the database via record types and optimize the performance.