record.submitFields() not working in catch(e){ } block in my M/R script. trying to set any script processing errors in a custom text field field on the record being processed instead of having to sift though script execution logs. Will record.submitFields() not work in a catch statement?

should work fine unless you ran out of points

it logs any error just fine in in my context.write() log. I don't think I am out of governance points..

what does the rest of the code look like

I believe that if you have declared your object used for the record.load in the try block, that would mean that the variable is not in scope of once you get to the catch block. If you declared the object outside the try block, you should be able to use it both in the try and catch blocks.

the record object is loaded outside of the try block

your error handling code has no error handling

@battk should I move the record.submitFields() into the summarize function? if not what do you suggest I do?

it isnt

that context.write() in my map stage is working as it should and logging any and all errors, that are getting passed to the summarize stage already. my problem is definitely not being aware of any errors. the problem is posting the error to the specific record it is processing via the record.submitFields()

implement the logging i linked you

I see in you are referencing the packingListId in the catch block. you have that variable declared in the Try block. That variable is not in scope to be used in the catch block. Declare that variable befor the try block, assign it's value in the try block, then you can use it in the catch block.

@Th3VanMan That is what I needed to hear. thank you

I think tools like ESLint’s block-scoped-var rule will catch problems like this. A good linter will catch a lot of mistakes and save you considerable time avoiding bugs in the long run.