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

Resolved PBDOM bug?

  1. Issue
0
Votes
Undo
  1. Kevin Ridley
    Kevin Ridley
  2. PowerBuilder
  3. Monday, 16 December 2019 20:58 PM UTC

Has anyone been able to use the PBDOM_Element.GetChildElement method successfully in PB2017?  I'm using PB2017 R2 currently, won't be migrating to 2019 until R2 is GA.  Anyway, I have an element with 5 sub elements.  I'm able to get all of the sub elements using GetChildElements method, and when I loop through the array returned, the element I'm looking for is in there.  But when I do GetChildElement and pass the element name, I get null returned.  This seems like a bug to me.  Anyone got the GetChildElement working successfully?

Do I have to replace my SOAP Connection webservice...
pbdwe170.dll failing after Windows upgrade
Responses (2)
Michael Kramer
Michael Kramer Accepted Answer Pending Moderation
  1. Monday, 16 December 2019 22:14 PM UTC
  2. PowerBuilder
  3. # 1

Hi Kevin,

Can you sanitize the XML content so you can share the issue-ridden data with me? Reach out via e-mail or LinkedIn in case you want to share in a more private setting. I would be happy to see if I can repro.

Due to hardware crash I have completely new Win10 machine with completely new installs of PB2017 R3 and PB2019 GA so I have a nice testbed for now. Until I install next PB 2019 R2 beta.

Happy to help if needed. /Michael

Sidebar: Running Win 10 as "early bits insider" so I can verify whether next Win10 release impacts your scenario.

Comment
There are no comments made yet.
Ken Guo @Appeon
Ken Guo @Appeon Accepted Answer Pending Moderation
  1. Tuesday, 17 December 2019 02:55 AM UTC
  2. PowerBuilder
  3. # 2

Hi Kevin，

I tested locally but didn’t encounter the issue you mentioned. The GetChildElement() function can retrieve the Child Element successfully.

I suggest you check whether the parameters in the GetChildElement() function are the same as the element name in XML, especially the case difference because it is case-sensitive.  

If the issue still exists after the above, please submit a bug in Appeon Support ticketing system (https://www.appeon.com/standardsupport/newbug) and also provide a small reproducible case for us while submitting the bug. Thanks in advance.

 

Regards,

Ken

Comment
Kevin Ridley
  1. Kevin Ridley
  2. Tuesday, 17 December 2019 22:26 PM UTC
Bug 3782 created
  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.