No data produced from map

Document created by mike_c_frazier Employee on Jul 2, 2013Last modified by Adam Arrowsmith on Mar 14, 2017
Version 5Show Document
  • View in full screen mode

Error

No data produced from map xxxxx please check source profile and make sure it matches source data.

 

Cause

This is a common error that typically occurs when either:

  • The incoming document does not match the source profile referenced in the map
  • None of the mapped fields actually contain a value resulting in no output document created

 

Solution

 

Source Data Mismatch

  • If you are retrieving data from an application connector with a response profile defined in the Operation component (e.g. Salesforce, Database, NetSuite, etc.) make sure the same profile is referenced in the Map. For example:
    • Below is a map with the SF_Account_QUERY_Response profile referenced:
    • Double check to make sure the profile in the operation that retrieved the data is the same:
  • Tips for Flat File data:
    • For delimited files, make sure the number of columns in the file matches the number of elements defined on the profile. Some common issues found in delimited flat file such as a comma-delimited CSV file that result in column mismatch include:
      • Make sure there are no unescaped commas in the actual data values that result in additional columns. If there can be commas present within data values, those columns must be properly escaped, typically with double quotes.
      • Similarly if there can be line breaks present within data values, those columns must be properly escaped.
    • For data positioned files, double check the start column and length for mapped elements. Remember the first position on the line is 0 not 1.
    • Make sure the actual data and profile configuration align with respect to Column Headers. If the profile expects column headers it will ignore the first line of data. This can happen when splitting flat file data with column headers by line and not selecting the option to "Keep Headers".
  • Tips for EDI data:
    • Make sure the delimiter and/or segment terminator in the data matches the options defined on the profile.
  • Tips for XML data:
    • Make sure the root element matches that defined in the profile.
    • If namespaces are used, make sure those are configured appropriately within the profile.
  • Tip for JSON data:
    • Make sure the root element matches that defined in the profile. One common scenario is when a query operation may return one or more records and the actual data may either begin with a single object or an array of objects. These need to be handled by separate profiles.
  • Tips for Database data:
    • Make sure it is the exact profile referenced in the Database query operation. The document data actually contains a reference to the profile's component ID.
  • Additional troubleshooting tips:
    • Pay extra attention if you are manipulating the documents between the connector operation and the map. This includes using Data Process shapes (e.g. split, combine, custom scripting) or Message shapes. Be sure to carefully inspect the source data passed into the map shape to make sure it matches the source profile.

 

No Values Mapped

Carefully compare the mapping rules to the source data to make sure at least one source element is populated, or if there are any Default Values configured on destination profile elements.

3 people found this helpful

Attachments

    Outcomes