Lawson Infor Process Automation XML Builder/Parser node with error – ‘X is not defined’
Summary of issue: When working on a Lawson IPA Flow issue, there was an IPA Webservice Node call that grabs XML data. This data was then fed into an IPA XML Builder/Parser node and begin to throw an “’X’ is not defined” error.
After our IPA WebSvc node “getNewlyAddedContacts” made an API call to return records. It then fed to an XML Builder/Parser node and threw a “’P1’ is not defined error”. We will explain why below.
Even though the “contacts” information was being called successfully, one of the records had bad data.
This record specifically had a { (bracket) in one of it’s fields and this somehow got encoded as {
Which resulted in the XML Parser Node in IPA to fail with the “P1” is not defined error.
So, if this happens to your process that is calling on XML formatted data, search your logs for the specific record that “is not defined”.
Good luck!
Retiring Lawson, PeopleSoft, or Oracle? APIX archives the entire application — every table, every year, attachments and security included — into your own AWS account in about 30 days, so you can decommission the legacy system and keep full access to the history.
