E-QR: Query Generated XML Or JSON File Contains Different Tag Names After Applying The PT 8.55.13/8.55.14 Patch
Last updated on APRIL 28, 2017
Applies to:PeopleSoft Enterprise PT PeopleTools - Version 8.55 to 8.55 [Release 8.4]
Information in this document applies to any platform.
The purpose of this article is to notify you about a change in the way PeopleSoft Query generates its XML data, upon application of the PeopleTools 8.55.13 or 8.55.14 patch. This has the potential to impact any process/job/report that consumes/utilizes the XML data. In particular, it can cause existing BI Publisher Reports to generate empty reports.
The 8.55.13 and 14 patches, introduced a change in behavior with regards to the way Query generates its XML data. The rules determining whether or not aliases are included in the XML tag names (eg., <A.DEPTID>, <A.EFFDT>, etc.) were modified, potentially causing the XML data to no longer include the aliases in the tag names (eg., <DEPTID>, <EFFDT>, etc.). As a result, the following are areas where the change in behavior may be observed:
1) Running BI Publisher Reports based on Query Data Sources
BI Publisher reports using Query data sources will no longer generate any data in the report output, if the field name mapping defined in the template no longer matches the XML data generated by the underlying Query.
2) Running QAS Services to generate XML or JSON output
Running a Query via QAS (PeopleSoft Query Web Services), using either REST or SOAP based requests (eg. “QAS_EXECUTEQRY_REST_GET”, or “QAS_EXECUTEQRYSYNC_OPER”), and specifying “XMLP” or “JSON” as the output type.
3) Running scheduled Query to XML output
Scheduling a query to XML output, and specifying “XMLP” as the output format. The webrowset-based “XML” output format however, is not impacted.
4) Running Query to XML via PeopleCode
Running a Query via the Query Peoplecode Apis RunToString() and RunToFile(), will also be impacted, when specifying constant %Query_XML_XmlP as the output format parameter (numeric value 20). If specifying constant %Query_XML_WebRowset (17), the XML will not be affected.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms