As of December 1, 2020, Focal Point is retired and repurposed as a reference repository. We value the wealth of knowledge that's been shared here over the years. You'll continue to have access to this treasure trove of knowledge, for search purposes only. Moving forward, myibi is our community platform to learn, share, and collaborate. We have the same Focal Point forum categories in myibi, so you can continue to have all new conversations there. If you need access to myibi, contact us at myibi@ibi.com and provide your corporate email address, company, and name.
(Edit: I had to change the < > to { } because the excerpt was not showing up. The original file is enclosed with < >.)
The tags have a prefix "agn" or "ext". I have completed a plan with another XML file that does not have the prefixes and it reads and transforms it with no issues, but it seems like the prefixes cause the object to not read anything.
I have already tried the "Namespaces" section in the XML Reader object and that did not seem to work.
Any input would be greatly appreciated. Thank you.This message has been edited. Last edited by: FP Mod Chuck,
Posts: 3 | Location: Virginia Beach, VA | Registered: March 11, 2020
I am by no means an expert with DQS and XML so I asked one of the tech support people to look at this post. His reaction was that your xml is an unusual looking document. People usually use < > brackets, Not { } , which is what I’m seeing Eg {agn:Party id="Party_00000000"}
That would be something you’d expect to see in a JSON file..
So the suggestion is to change the { } brackets to < > brackets and see if that helps. If not please open a case with techsupport.
Thank you for using Focal Point!
Chuck Wolff - Focal Point Moderator WebFOCUS 7x and 8x, Windows, Linux All output Formats
Posts: 2128 | Location: Customer Support | Registered: April 12, 2005
I am by no means an expert with DQS and XML so I asked one of the tech support people to look at this post. His reaction was that your xml is an unusual looking document. People usually use < > brackets, Not { } , which is what I’m seeing Eg {agn:Party id="Party_00000000"}
That would be something you’d expect to see in a JSON file..
So the suggestion is to change the { } brackets to < > brackets and see if that helps. If not please open a case with techsupport.
So sorry. I didn't put a note in my post that I had to change the < > to { } because the post was reading it as code therefore not showing up. The original file does have the tags enclosed with < >.
Posts: 3 | Location: Virginia Beach, VA | Registered: March 11, 2020