Error: There was a failure executing the send pipeline: "abc" Source: "JSON encoder" Send Port: "xyz" URI: "" Reason: Input string was not in a correct format.

 Error: There was a failure executing the send pipeline: "abc" Source: "JSON encoder" Send Port: "xyz" URI: "" Reason: Input string was not in a correct format.

Issue:

While attempting to make a POST API call through an orchestration, I encountered the following error:
There was a failure executing the send pipeline: "abc" Source: "JSON encoder" Send Port: "xyz" URI: "" Reason: Input string was not in a correct format.


Root Cause: 
The error occurred due to an issue with the input payload. The field's data type was specified as xs:unsignedShort, but I mistakenly provided the input value "DC_NUMBER," which is an incorrect format. However, after correcting the input value to a numerical format like "00015925," the issue was resolved successfully.

Comments

Post a Comment

Popular posts from this blog

Error: Number of included segments do not match

Introduction In this blog, we tackle a crucial issue encountered during the reprocessing of an X12 EDI message. We will get into the root cause of the problem and provide you with a solution to overcome it. Error: An output message of the component "Unknown " in receive pipeline "Microsoft.BizTalk.Edi.DefaultPipelines.EdiReceive, Microsoft.BizTalk.Edi.EdiPipelines, Version=3.0.1.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" is suspended due to the following error:       Error encountered during parsing. The X12 transaction set with id '103465910' contained in functional group with id '02', in interchange with id '000000009', with sender id '4532345856     ', receiver id '8038025150     ' is being suspended with following errors: Error: 1 (Miscellaneous error) 4: Number of included segments do not match . The sequence number of the suspended message is 1.  Root Cause: The issue stems from a mismatch in the number of se...
Read more

REST API Calls with Query Parameters in BizTalk: A Step-by-Step Guide

Image
 Introduction In this blog, I will provide a comprehensive guide on how to call a REST API that requires query parameters. We'll walk through the necessary steps to set up the environment and make successful API calls. Solution High Level Steps 1. API Overview: We will be using an open API for demonstration purposes. The API endpoint we'll be working with is: https://randomuser.me/api/?results=1 2. Schema Creation: Create a schema named "SourceA" that matches the structure of the messages you'll be dropping in the receive location. To create a JSON response schema, follow these steps: capture the JSON response by running a test in Postman, and then utilize a JSON schema generator to create the desired JSON schema. 3. Field Promotion: In the SourceA schema, promote the field called "results." This field will serve as the variable for the query parameter. 4. Receive JSON Pipeline: Develop a receive JSON pipeline that can receive JSON messages and convert t...
Read more

Document flow in Boomi

Image
Document Flow in Boomi Each document may contain one or multiple records. Groups of documents move in a batch in Boomi. Boomi automatically loops through records and documents. Each path processes to completion before the next path begins. Different Shapes in Boomi Branch Processes entire deck of documents in each branch shape It executes each path sequentially. The documents flow down the subsequent paths only if the documents flowing down the preceding path succeed in completing the path A branch can have up to 25 paths Decision Sort the documents into 2 piles. The one which matches true is executed first and the other which matches false is executed last. Try-Catch This is used for error handling. All documents flow through the Try path. Failed document flow to the catch path Flow Control Batching Documents are batched into the specified size + remainder. For example you are batching by 5 documents and you receive 21 documents in that shape. It will be processed in batches in the ma...
Read more