This was by design. Please find the reason that our Product team has provided below.
Snaps decide which error are written to error views and which errors cause pipeline failure. The reason the decision was taken initially to fail pipeline on endpoint connectivity errors was so that we do not repeatedly retry an operation when the endpoint is down. So only data errors go to error view, connectivity errors cause pipeline failure. So if you have a million documents going to a DBInsert, we do not retry database connect a million times if the database is down
We currently have user stories open on this issue. Will keep the thread posted. Thank you.
Hi @Sahil,
You can use mapping to do this. Here is an example:
jsonPath($, “$Z_RDGD102.IDOC.DKA1[*].PAR”).map(x=>x == “AF” || x == “AG” || x == “PC”).toString()
Or, if you have multiple PAR objects in DKA1, and at least one should match the condition, than you can go with this:
$Z_RDGD102.IDOC.DKA1.filter(x=> x.PAR == “AG” || x.PAR == “AF” || x.PAR == “PC”).length>0
Regards,
Bojan
Hi,
I tried 1st option but I am getting below error:-
Failure: Unable to write to JSON-Path: $.Order.Data.Addresses, Reason: Expecting object or array for wildcard path, found: true,false,true,true,false,true, Resolution: Change the preceding path to refer to an object or array value
