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.
Join the TIBCO Community TIBCO Community is a collaborative space for users to share knowledge and support one another in making the best use of TIBCO products and services. There are several TIBCO WebFOCUS resources in the community.
From the Home page, select Predict: WebFOCUS to view articles, questions, and trending articles.
Select Products from the top navigation bar, scroll, and then select the TIBCO WebFOCUS product page to view product overview, articles, and discussions.
Request access to the private WebFOCUS User Group (login required) to network with fellow members.
Former myibi community members should have received an email on 8/3/22 to activate their user accounts to join the community. Check your Spam folder for the email. Please get in touch with us at community@tibco.com for further assistance. Reference the community FAQ to learn more about the community.
(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: 2127 | 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