Close popover
Michael Finlay (MichaelF1903)

MichaelF1903 Member since 2012 26 posts
Posted: August 1, 2019
Last activity: August 28, 2019

What benefit is there to use Saveable Data Page?

I have been using PRPC for many years and I am comfortable with the concept of using Obj- methods for standard read/write activities. I notice that from 7.4 onwards there has been a push towards using Saveable Data Pages to persist data. But I am struggling to see the advantages these add and wonder if I am missing something.

Looking at the complexities surrounding developing these (defining a data page, defining a load method, defining how to save it and the non-linear logic progression this implies), it seems less useful than the traditional methods. The only advantage I can see is that it works declaratively instead of procedurally. However, given the performance impact of declarative processing and the advice to avoid overusing it, is it really beneficial to use these Saveable Data Pages instead of controlling the saves programmatically? Is taking away power from the developer offset by convenience? And is it as reliable (declarative expressions occasionally do not fire, making them unsuitable for data that requires 100% reliability)?

I am open to conversion provided someone can show me a realistic use case where it outperforms traditional methods and/or is simpler to use (i.e. is it really better, or is it like Data Transforms that add nothing but increase complexity and maintenance effort?). And above all, can be shown that there are zero instances of Data Pages not saving when they should?

Any takers for my challenge?

Low-Code App Development Data Integration Java and Activities
Moderation Team has archived post,
Close popover This thread is closed to future replies. Content and links will no longer be updated. If you have the same/similar Question, please write a new Question.