Problem: The mapping to "Created From" is missing in flow. The flow proceeded to save the record, but NetSuite threw the error to reject the invalid date format.
Solution: Adjust the date format to allow the file to process into NetSuite.
If you look at the dashboard, you can see that the flow is ignoring what looks to be valid data.
This usually indicates that there is a disconnect somewhere between the sample data what Integrator.io uses to determine the layout of the file to be mapped into NetSuite and the actual data that is being received. Looking into the flow settings you can see that the flow is configured with the following sample data:
In this case, it appears to be only column header values and no actual data. Comparing this to the initial data, it shows that the header values in the data were different from what Integrator.io was set to expect.
- Update the dateFormat issue by using YYYYMMDD HHmmss as the format. Previously, it was YYYYMMDD hhmmss, but it appears that the data is sent as 24 hour time.
- A script (NetSuite file id: 154746) is loaded in the flow SuiteScript Post Map hook. In it there is a class DeltaQuantitySetter checking whether the field "celigo_nlobjTransformId" (same as NetSuite native field "Created From" on the item fulfillment record) has a value. However the mapping to "Created From" was missing in the mapper. The mapping is now added to mapper so the flow did not ignore the record anymore.
- While the flow proceeded to save the record, NetSuite threw the error to reject the invalid date format. IO mapper is not able to parse the format of "YYYYMMDD hhmmss" but some other formats are supported.
- If it appears that there is extra data that is mapped that is not necessary to identify the item to be fulfilled, those other fields would likely need to be removed in the Mapping. For an item fulfillment, generally there are only a few things required on the line level field mappings. You'll need something to identify the item or the line, but usually not both. In this case, the SKU might be acceptable. You'll also need the quantity of the item(s) to be fulfilled. Lastly, you'll also want to map any custom data points, if needed. For the header level, a reference to the sales order and any other required fields are necessary.
- A general rule of thumb when testing mappings is to start by mapping only the least amount of data that's necessary to create/transform the record, and then start adding any extra data (custom fields, notes, etc) once the "bare minimum" record gets created by the dataflow.