Hi Guys,
I my application frequently uses customer data in multiple screens and reports. Would a keyed data page be a good choice for managing this data? What are the trade-offs compared to using a regular (non-keyed) data page?
Regards,
Niharika
Hi @DADIN007,
A keyed data page is a good choice for managing customer data in your application when you frequently access individual customer records across multiple screens and reports. It allows efficient, on-demand loading and caching of data per unique key (e.g., CustomerID), improving performance and reusability without reloading the same data repeatedly. Compared to a regular (non-keyed) data page, which loads all data at once or stores a list, a keyed data page offers better memory efficiency for single-record access but can lead to higher memory usage if too many keys are loaded in a session. It’s ideal for scenarios requiring frequent, selective access to specific customer records rather than bulk data retrieval.
Thanks,
Hema