Skip to main content

This content has been archived and is no longer being updated.

Links may not function; however, this content may be relevant to outdated versions of the product.

The data flow cannot parse JSON records

Suggest edit Updated on September 10, 2021

The following exception occurs when you start processing a data flow run:

Cannot parse JSON <specific information about a data flow shape>

The error message usually points at the Source shape of type Stream in the data flow rule as the place where the error occurred.

Cause

This error is caused by incorrectly formatted JSON input records in the data set.

Solution

To eliminate this error, perform the following steps:

  1. Review the error details to find which shape in the data flow contains the incorrectly formatted JSON input records that caused the error. For more information, see Tips for troubleshooting data flow rules.
    Click View input record to view the record that caused the error.
  2. Update the JSON formatting based on the root cause of the error.

Example

The following example input record contains incorrectly formatted JSON:


<pagedata>
 <pyFaultReason>
  { "CellIdCaller": "1", "CallRecipient": "1", "CellIDRecipient": "1", "CallDirection": "1", "SubscriptionID": "S-892","TerminationCode": "1", "CallDuration": "20", "CDRMapping": {} "CallID": "1"
 </pyFaultReason>
 <pxObjClass>Embed-Error</pxObjClass>
</pagedata>

The following example error message identifies the root cause of the incorrect formatting:


Caused by: com.fasterxml.jackson.core.JsonParseException: Unexpected character ('"' (code 34): was expecting comma to separate OBJECT entries
at [Source: com.pega.dsm.dnode.util.ClipboardPageJsonConverter$ByteBufferInputStream7158ccb7; line: 1, column: 185]

Based on the above examples, you can conclude that the error is caused by a missing comma between the CDRMapping and CallID properties in the JSON input record.

  • Previous topic The Predictive Analytics Director portal is unresponsive
  • Next topic The pyApplication and pyApplicationVersion properties are not captured in the interaction history
Did you find this content helpful? YesNo

100% found this useful

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us