Notifications

47 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

Intended Fix Version

Orlando

Safe Harbor Statement

This "Intended Fix Version" information is meant to outline ServiceNow's general product direction and should not be relied upon in making a purchasing decision. The information provided here is for information purposes only and may not be incorporated into any contract. It is not a commitment, promise, or legal obligation to deliver any material, code, or functionality. The development, release, and timing of any features or functionality described for our products remains at ServiceNow's sole discretion.

Associated Community Threads

There is no data to report.

Article Information

Last Updated:2019-05-21 11:43:53
Published:2019-05-14