We are using below statement for creating XML and passing this string to Oracle DB, however few of our customers who are on older version of Powerbuilder (less than PB 12.5)have reported issues with regards to data not saved, root cause was String XML had no data in it. None of our customers have reported this issue on higher versions.
ls_String = dw_1.Object.DataWindow.Data.XML
Does this statement generates some kind of temp file on system, unable to do so due to restricted access may cause the above issue? or is it an issue of Powerbuilder version?
Could you please suggest how can we overcome this issue.
Suspecting the old powerbuilder version we had replaced the datawindow.xml statement with the code which forms the XML in the similar fashion.
Our customer is in the process of migrating to 2017 and then to 2019 R1, but we need to be sure we do not have to do the workaround fix for them. This is why i am trying to get to the root of the issue on basis of which we can take a decision.
Thanks for your quick response.