Skip to main content
aswinkarn418986
aswinkarn418986
June 8, 2022
Question

RecordType Faster than QueryEntity

  • June 8, 2022
  • 4 replies
  • 0 views

When I tried to get data using a query filter for a custom picker and when I tried using record picker, I could find a significant performance difference. Record Picker was very fast when compared to a custom picker. How does record picker work and can we do the same for a custom picker also? And I  would also like to know how record type actually holds the data, is it like a cached memory or it fetches every time? Can someone help me understand this?

4 replies

stefanhelzle0001
stefanhelzle0001
Brainy
June 8, 2022

https://docs.appian.com/suite/help/22.2/records-data-sync.html

This should give you a good start.

Can you post the code for your slow custom picker?

aswinkarn418986
aswinkarn418986Author
June 17, 2022

I used the same code from Appian documentation

davel001150
davel001150
June 8, 2022

What Appian does is cache your data in the record type in memory or RAM.  You control when the cache is updated, and they're improving it all the time.  Since you only have to pull it from memory, it's faster than trying to pull the same information from the DB.

The whole goal was for synched records to be a lot faster.  It's possible that you can get exactly what you need from record picker provided you have all the relationships and custom fields and logical expressions set up correctly.

    aswinkarn418986
    aswinkarn418986Author
    June 17, 2022

    So if we are having many recordtype does that affects the system? From my understanding, RAM or cached memory will have less memory when compared to DB. So if we have many record type or one recordtype having many rows(eg:more than 1 lakh rows), does this have an impact on performance? And I do have one other question, If we have a 2 tables which together has more than 100 columns, what is the best practice to create a record type? [mention:f392a8ed25f84233ae21b9c8ffc07b88:e9ed411860ed4f2ba0265705b8793d05]

    Terms & ConditionsAccessibility statement