Question
How Savable data page works internally during update/insert
Folks,
Would like to know how Savable data page works internally. I was trying to turn on the trace to see the actual SQLs behind update/insert via Savable, but couldn't get a clue.
Appreciate your help !
Thanks.
Yeha, Had gone thru the KB, But couldn't find the material I'm looking for. I would like to know what SQLs run against database when savable data page pitches-in ( I tried to trace it but couldn't) or Savable data page internally calls OOB Activities ?
Depending on your configuration, the Savable Data Page won't send the SQL to the database until there is a Commit event, no different than using Obj-Save.
If you are experimenting by having an Activity that calls Save-DataPage and running that activity from Dev Studio then the save may be queued but never sent.
Use the Save Data Page options from a Flow or Flow Action to see more real world usage. Also, run the Studio Tracer with the "DB Query" event turned on to get a better sense of when the SQL is sent as well as what the SQL is.
"If you are experimenting by having an Activity that calls Save-DataPage and running that activity from Dev Studio then the save may be queued but never sent." - Very interesting, let me shed some light on this. Thanks !
Hello,
Have you already seen the following: https://community.pega.com/knowledgebase/articles/data-management-and-integration/84/savable-data-pages