Could someone please help me understand the difference between data Sync and immediate data sync for record type.
I was referring "https://docs.appian.com/suite/help/20.4/Record_Type_Object.html#data-sync
Under "Data sync" the below criteria is given:
You should only enable sync for your record type if:
Where under the topic "Updating synced record types" it talks about immediate update?
Discussion posts and replies are publicly visible
Thank you very much Peter and Marco and juergeng. You have nicely explained this. I have no doubt now.
If DataSource for any record is Database view (data might be coming from different table) then how sync will work..I mean if any table involve in view is updated then data will be refreshed ?
No. Appian does not know about updates in your view. Would a scheduled resync work? With 21.2 you might be able to build that view inside Appian with synced records. Then data would always be up-to-date.
Yes Stefan ,in 21.2 they will have relationship concept among different records. But not sure how to handle sync for the existing record with datasource as View. It the most common practice till now. As per documentation only table can be synced not the database view.
You cannot select a database view as the source for a synced record type. So, you can either leave the existing record type as is or create a new one that directly goes against your source table.
Just curious - what functionality do you have set up in your DB view?
Thanks Peter. Our existing DB views are getting data from different tables with customization on some selected columns. So the case is where record involved data from multiple tables.
Thanks for the clarification! Luckily I think you should be able to meet that use case with the upcoming features in 21.2 for related records and custom fields!
Yes. I saw presentation on related records and custom fields in Appian world .That might help. But not sure in that case we need to create the multiple records and then only we can do relationship among records not directly on tables. This may end in creating unnecessary records (with single table as source) just for relationship.
I don't see these as "unnecessary" records at all - it's just a different approach to using data . Think about CDTs, you have a CDT for every single table you need to query, right? Why not do the same with record types? You can decide which record types are exposed via Tempo or Sites, so record types that are only used for reference data don't need to be exposed to users. Think of the record type as both a mechanism for building record lists / views AND a way to model and access your data.
Thanks Peter, this is exactly what I currently try to wrap my head around regarding impact of new records on my solution designs.
Yes I am agree Peter. It is going to be new approach to solution design.
© 2022 Appian. All rights reserved.