Subscribe via RSS
Toggle Submenu
  1. Categories
  2. Recent
  3. Tags
View Replies (2)

Resolved dw1.Object.DataWindow.Data.XML

  1. Issue
0
Votes
Undo
  1. rohit ranjan
    rohit ranjan
  2. PowerBuilder
  3. Tuesday, 11 August 2020 15:25 PM UTC

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.

PostgreSQL: "Select Data Source" pops up with eve...
TLS 1.2 when using SNC SQL Native Client(OLE DB) a...
Responses (2)
rohit ranjan
rohit ranjan Accepted Answer Pending Moderation
  1. Saturday, 22 August 2020 09:36 AM UTC
  2. PowerBuilder
  3. # 1

Hi Chris,


Few of the customers have reported this issue on PB-2017, while for most of the customers it is working fine. We know this issue goes away with providing access on the directories, but customers are reluctant on providing access to the directories, also we haven't been able to point which directory requires access.


We are using below statement to generate the XML, and datawindow DataExport has been set as seen in the below screenshot.

There should be more logical solution other than forming the XML via code. Please suggest.

String ls_Xml 

ls_Xml = dw_1.Describe("DataWindow.Data.XML")

 

 

Comment
Chris Pollach @Appeon
  1. Chris Pollach @Appeon
  2. Saturday, 22 August 2020 18:17 PM UTC
FYI: Both the DOT notation & Describe() method are in memory operations. No temp files. The folder access is when you write the XML data stream to disk or when you use the SaveAs(XML!) command.
  1. Helpful
There are no comments made yet.
Chris Pollach @Appeon
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Tuesday, 11 August 2020 15:34 PM UTC
  2. PowerBuilder
  3. # 2

Hi Rohit;

   Sounds like you need to migrate your older PB Apps from Sybase to Appeon. Especially, since Sybase & SAP versions are no longer supported.

Food for thought.

Regards ... Chris

Comment
rohit ranjan
  1. rohit ranjan
  2. Tuesday, 11 August 2020 15:52 PM UTC
Hi Chris,



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.
  1. Helpful
Chris Pollach @Appeon
  1. Chris Pollach @Appeon
  2. Monday, 17 August 2020 16:13 PM UTC
Hi Rohit ... have you tried the <DW Control Name>.Describe("DataWindow.Data.XML") command instead?
  1. Helpful
There are no comments made yet.
  • Page :
  • 1


There are no replies made for this question yet.
However, you are not allowed to reply to this question.
We use cookies which are necessary for the proper functioning of our websites. We also use cookies to analyze our traffic, improve your experience and provide social media features. If you continue to use this site, you consent to our use of cookies.