Validation to identify non-existent XML data sources
I am currently building a new template with changing XML data sources and values.
The values prove to be no issue as the new data is simply pulled into the Output.
However, if the XSD/XML changes, say the data point name, then the Output just ignores the Autotag ie. null value inserted in Output. The validation tool doesn't identify 'broken' Autotags and actually states that the validation was successful. This also applies to the 'Preview' button, which returns a null but doesn't mention that the data point couldn't be found.
Steven Braithwaite
shared this idea
Hello Reporter,
We have reviewed this idea internally but it has been declined for development due to a lack of votes. Thank you for your suggestion, and please submit any other ideas you have to improve the product.
Adam Austin
Product Manager
-
Adam Jackson
commented
Hi Steve,
Thanks for your request. I am happy to tell you that we have a new tool coming out soon called Verify that you can use to check for Null entries in your data source, along with a lot of other Error Handling functionality. Additionally, you'll be able to mark the responses as Warnings or Errors, both of which can be viewed in AutoTag as well as an Engine API call we are adding. Look for this feature in the next month or two in 15.1, and let us know if you have any questions in the meantime.