I designed a table as list to save records. I want to save the changes in the table and add new records.
D_FixtureList.pxResults are visible to all unsaved record and changes. I want to save this D_FixtureList.pxResults list to Fixture datatype. I worked with data transform and activity on Savable Data Page. But it did not work. How I configure with this problem ?
If from a Flow or Flow Action then Pega's engine will orchestrate a Commit when the next assignment is reached.
If from an Activity - which perhaps you are testing in isolation - you will need to ensure that something is performing a Commit. Otherwise the Savable Data Page behaves as per an Obj-Save - that is, it is queued to be saved but something needs to subsequently Commit the deferred saves.
Trace the interaction where you are expecting the Savable Data Page to be saved, ensuring the "DB Query" event is turned on, and make sure you can see the Savable Data Page save rules being run and that something is orchestrating a Commit. Perhaps for your unit testing, implement a Draft Flow that uses the "Save Data Page" automation so as to ensure that - when part of a Pega transaction - the Savable Data Page performs as expected.
Hi @AsenaGokceA, I also faced same issue instead of creating id in activity, use savable data page source option as data transform and create id, copy your data from source page (D_FixtureList.pxResults(1).availabiity) to target (primary page-data page (.availability)). Like wise you can copy all your data into target page.