-
Jim Reese
- PowerBuilder
- Tuesday, 21 April 2026 09:36 PM UTC
We ae upgrading from 2022R3 to 2025 and Migrating PFC from version 12 to the current 2025 open source version. Until now, we have been using PBDOM2022.pbd for pbdom functionality.
We see with the newer PFC, the pbdom wrapper objects have been added to PFCapsrv.pbl. However, pbdom_document is missing 2 XML functions, SetXMLDeclaration and GetXMLDeclaration, and we do use SetXMLDeclaration. So when we try to either edit the pfc object (not good practice) or create a PFE layer version (not a true descendent, just the same name higher in the tree with the missing functions added), the pbdom_document object won't compile, it fails on GetOwnerDocumentObject which happens to have a return type of pbdom_document, saying the return type doesn't match the ancestor. The ancestor is pbdom_object, which also has the GetOwnerDocumentObject function, which also has the return type of pbdom_document. Also, without saving the object, due to the compile error, the pbdom_document object drops from visibility in the pbl. Optimizing the pbl will report that the source is found, but not the object, and offer to export the source. Renaming or removing the GetOwnerDocumentObject function in pbdom_document does allow the object to be modified and saved. The object then does still show the ancestor GetOwnerDocumentObject in the function list, inherited from pbdom_object.
Comparing the source of the pfcapsrv.pbl version and the pbdom250.pbd version, the only differences are the 2 missing xml functions, and the global type line identifying native "pbdom.pbx" is lowercase in one, uppercase in the other.
Has anyone else experienced this, or have a suggestion for resolving this? For now, we have chosen to remove the pbdom objects from pfcapsrv.pbl, and continue to use the pbdom250.pbd that Appeon provides, but we were hoping to not have to make changes to the PFC layer objects.
Find Questions by Tag
Helpful?
If a reply or comment is helpful for you, please don’t hesitate to click the Helpful button. This action is further confirmation of their invaluable contribution to the Appeon Community.