In RD how will u fetch a case and save it in it not using data page so that instead of making call to db again and again it uses RD

General
1

In rd how will u fetch a case and save it in it not using data page so that instead of making call to db again and again it uses RD,the client wants it via RD only not to use any other DataPage,is it even possible to configure this in a RD?

2

In RD, we can fetch exposed DB columns (we can fetch non exposed columns too, but its not suggested). But in case you can have pages , page lists etc., in BLOB, you can’t fetch them using RD. So, you cannot always fetch an entire case using RD itself.

3

This is not recommended best practice. Iteration the result set and perform the DB operations using Obj-Open-By-Handle, Save and Commit.

4

Hi Tanya,

A Report Definition by itself is read-only — it queries data but has no built-in mechanism to save or cache results.

Approach 1: Savable Data Page + Report Definition (Recommended)

This is the cleanest, low-code approach with built-in caching.

Approach 2: Data Transform

Use when you need to transform or map data before saving ( Clean mapping logic, reusable, easy to maintain)

Approach 3: Activity (Legacy / Complex Scenarios)

Use when you need procedural logic, bulk operations, or complex conditional saves.

Note: Always prefer declarative (Data Page / Data Transform) over procedural (Activity) when possible.

5

hi @RameshSangili so if we are using an activity as well still the DB will be hit right,but the scenario that i was asked was the db should not be hit multiple times how to configure RD in such a way that it caches the data within it instead of again and again calling the Db to fetch the data without using Data page.

6

@TanyaS58 Apologies, I misunderstood your question. Now, my understanding is you want to fetch some data using report definition and use it somewhere and don’t want to hit DB multiple times. I don’t think using only report definition, we can achieve such a requirement. If we really want to use only report definition in an activity and achieve it, While the activity is running for the first time copy the results of report definition into some temporary page. Whenever the activity runs for next time, check the condition to see if this temporary page is already populated and only run RD if this page is empty. This way it can reduce DB hits but only in that thread context as temporary pages are part of that thread. But this is highly not recommended, as there is a better option of data pages which are highly suitable is to serve these kind of requirements.