Creating my first function(s). I am calling a function from another function. It is very possible that the called function will hit an exception. I am been trying to get the called function to pass back the exception to the calling function (try/catch), store that for now in a variable and contin…

[image] utaylor: ” I always thought if an exception hits, the loop is over, is that not true? You put the code in a try catch. If it bombs in the try, then you hit the catch, where you send back the exception and make success false. [image] slitzau: That may be more for Widget type funct…

[image] slitzau: I am been trying to get the called function to pass back the exception to the calling function (try/catch), store that for now in a variable and continue processing the next record. I have been successful in getting the exception message back to the calling function using callCo…

[image] Banderson: What we’ve done is adopt a pattern where every function returns a Success boolean and a ErrorMessage string, so that wherever it’s called, the consuming code can decide if it wants to check for success and continue or not. Samsies. Every function returns oSuccess and oMessa…

Thanks for the replies, I ended up doing somewhat the same thing, check for the exception in the called function and return the message back to the calling function but I am using callContextBpmData so that I can also get the entire error message back. It sounds like you and @Banderson are using s…

If you do get an exception back Scott, how do you tell it to proceed and not bomb out? The same question to you @Banderson you mentioned that “it can decide if it wants to continue or not…” I always thought if an exception hits, the loop is over, is that not true?

The way I am doing it I am passing back any error message encountered through callContextBpmData.Character02, if that is a empty string no error encounter, if not then what is the error and then proceed with handling that exception in the calling function. But I want to test out the oError, oSucc…

So in other words the function will continue even if there is an error so you are capturing the error param from a method call in call context and passing it back to check if you should exit the loop?

The called function has a try/catch so in the catch I populate callContext and exit that function and then it depends in the calling function what the exception was and proceed accordingly in that function.

I see, you are doing it in code. I was wondering how to handle this with custom widgets.

Thanks for the explanation :pray:

Function Exceptions

Epicor ERP 10

cfinley (Chance Finley) July 26, 2021, 12:35pm 2

Not that its the exact solution you are looking for, but i created something similar with a UBAQ and BAQ Export to process quote expiration.

It doesn’t check if a sales order is available. It simply checks if the current task is losable and marks it.

Topic		Replies	Views
Proper Function Exception Handling (help) Kinetic ERP	18	2653	April 25, 2023
Let's Get Funcy - Epicor Functions Epicor ERP 10 e10	83	35991	July 4, 2024
Function error logged Epicor ERP 10 functions	14	3728	March 25, 2022
Call Function with a button click Epicor ERP 10 e10 , epicor , customization	29	6431	December 14, 2023
Function Fails when Calling Another Function in same library if it requires transaction Kinetic ERP epicor , function , functions	19	3205	November 7, 2023

Function Exceptions

Related topics