I have asked two developers about the best approach for data management in Appian.
One usually uses Datastore Entities and other uses Sync Recordtypes. But, I have seen that there is a third configuration where a RecordType is related to a Datastore Entity (this disable recordtypes relationship).
Which best approach is my dilemma.
I have heard recordtypes limitations related to database (some datatypes capacity limits) schema, 2 millions rows storage limitation and sync issues.
I haven't found documentation about best practices for data management.
What do you recommend? Some prefers CDT others Recordtypes.
Discussion posts and replies are publicly visible
With the way Appian is evolving, in my opinion using recordtypes makes your application future proof and also make your enviornment fit for Process HQ and other new features being introduced by Appian. Right now limitation is 4 million records. but with right filters you can sync lot more data. They have also planned to get the limit increased to 10 million.
In that context. Is there any documentation related to split up data in recordtype based on a date field just like it is explained in this video in minute 02:02 youtu.be/FvA3oezAVcg
Not that I have come across.
Hi Darwin Pou ,
In the video at 02:02, they discuss the Source filter (also known as the sync filter). For more information, refer to the below documentation.
Records-filter-source-data
For more comprehensive information on data fabric and its usage, please refer to the documentation below.
Data-fabric
Hi. In sync recordtypes what are the approaches when there are several apps that need to access the same data? Write and read. How the concurrence is handled if data is synced in distinct data fabric. When data in an app is read and another is writting at same time, so the first one is obsolete?
In database design is called concurrency control.
Data Locking Strategies have a look at this article by Appian. This might be of some use to you.
Thanks. Pretty nice. But what about I have a Record type in my app and it is need to be used by anothers appian app? Or maybe the data synced is updated by third partes in the database.
If the record is being updated by one appian app and being consumed by Appian then I don’t see a problem of data being obsolete . Yes if there is a third party is updating the data then you would need some type of trigger to sync the record. May be a webApi to inform that data has been updated and you need to sync the record again
Any article related to the whole design concept?