Data Source Error on Data Stream

Moretea
Tera Contributor

We are using the integration hub data source - data stream to load a SOAP message, but when we try and load the first 20 records in the data source, we get error message "No fields provided for mapping to headers". When the data stream action is ran in the flow designer it returns the expected results as per the screen shot, but as soon as try and run the data stream within the data source we get the above error message. I can't find any posts on community that help with the solution especially for XML parsered SOAP message.

 

2 REPLIES 2

Swarup Patra
Kilo Guru

This issue might be due to the incorrect configuration of the data stream or data source. Here are some steps you can follow to troubleshoot and resolve the issue:

1. **Check the Data Stream Configuration**: Ensure that the data stream is correctly configured to parse the SOAP message. The data stream should be able to parse the XML response and map it to the correct fields.

2. **Check the Data Source Configuration**: The data source should be correctly configured to use the data stream. Make sure that the data source is set to use the correct data stream and that the field mappings are correctly set up.

3. **Check the SOAP Message**: Ensure that the SOAP message is correctly formatted and contains the necessary fields for mapping. If the SOAP message is missing any fields or is incorrectly formatted, it could cause the error message.

4. **Check the XML Parser**: If you are using an XML parser to parse the SOAP message, ensure that it is correctly configured and is able to parse the SOAP message.

5. **Test the Data Stream**: Run the data stream in the flow designer and check the results. If the data stream is able to return the expected results in the flow designer, it should be able to do the same in the data source.

6. **Check the Error Message**: The error message "No fields provided for mapping to headers" suggests that the data source is not able to find any fields in the SOAP message for mapping. Check the field mappings in the data source and ensure that they match the fields in the SOAP message.

7. **Contact ServiceNow Support**: If you are still unable to resolve the issue, consider reaching out to ServiceNow support for further assistance. They may be able to provide more specific guidance based on your particular configuration and setup.

Remember, the key is to ensure that the data stream and data source are correctly configured, and that the SOAP message is correctly formatted and contains the necessary fields for mapping.


nowKB.com

Eric B2
Tera Contributor

How did you solve this issue?