330 views

Description

Discovery pattern fails.

In Pattern Log, it's showing error:
parsing input has failure, trying to attempt with prefeix <Root> 

In pattern debug, the step has below error popped: 
CUSTOM PARSING parsing strategy of output text failed due to an unsupported text format

JSON translator to XML was incorrect.

Steps to Reproduce

  1. Go into Advanced View for the Pattern Designer.
    2. Create a "Parse File Step."
    3. Enter Debug Mode with a Mid Server.
    4. Create a JSON file on a remote/host machine that breaks one of the following rules:
  • Elements that start with a number cannot contain letters
  • Elements cannot start with “XML”
  • Elements cannot have “-“ or most special characters such as “#”,  “@”, etc. for example:

{
"value": [{
"tags": {
"2018Demo": "GartnerDemo"
}
}]
}

5. Select that file on the debugger.
6. Retrieve File Content.


Workaround

JSON translator needs to conform to valid XML standards:

  • Elements that start with a number cannot contain letters
  • Elements cannot start with “XML”
  • Cannot have “-“ or most special characters such as “#”,  “@”, etc.

 


Related Problem: PRB1341778

Seen In

New York
SR - ITOM - CMDB CI Class Models - 201907
SR - ITOM - Discovery and Service Mapping - v1.0.35

Fixed In

Orlando

Associated Community Threads

There is no data to report.

Article Information

Last Updated:2020-11-16 09:53:49
Published:2019-05-14