You have two approaches, one is to continue on the path with a mapper and javascript methods, but you can use the filter method before map to only include the low risk.
$suppliersRisksResponseFromSupplierSAPI
.filter(x => x.aggregateRiskDetails.riskLevel == "Low Risk")
.map(x => x.riskDetails.supplierLocationStateCode)
The second approach is to use standard snaps to achieve the result, it may look more busy in SL designer but it is adding better readability and flexibility for the future if you want to work with other data from the input.
Attached is a sample, it will output the name of each low risk state as a separate document which you can work with or group as you wish.
Hello PSAmmirata
The same issue I am facing right now. my database account batch size is set to 50 and if error is in single record entire batch is getting error out with error message of first record where as other 49 records are valid records without erroneous data (tried and tested by manually removing 1 erroneous record ).
By setting batch size to 1 resolved the issue but now pipeline is taking 20 times more time as earlier ☹️
Kindly suggest me you came across any other better solution that would help me a lot.
Just adding to the chorus here. I am having the same issue. I am working to replace sqlldr, so, I am able to compare the same import between 2 methods. Snaplogic loads fine if the data is perfect. If there is any issue, in my case foreign key exceptions. It errors out a lot of good records with the same error code. The error clearly does not apply to a majority of the records (the parent does exist). The rejects do include the records that are appropriately rejected.
