Hi,
I have used error handling filters extensively in the following way:
1. create two display-only-fields:
- errorhandler errno
- errorhandler text
2. create two error handler filters
- errorhandler Message error
run if: ('errorhandler errno' = $ERRNO$)
action: message error: $errorhandler
Hi,
I have used error handling filters extensively in the following way:
1. create two display-only-fields:
- errorhandler errno
- errorhandler text
2. create two error handler filters
- errorhandler Message error
run if: ('errorhandler errno' = $ERRNO$)
action: message error: $errorhandler
Hi,
I have created a Filter Service that I call from a filter. The problem is
that data seems to be committed to the database even though there is an
ERROR later on in the processing.
A1. Modify Filter in form A: Call Service X
X2. Service Filter: pushes data to form X
A2. Modify Filter in
My understanding is that since you are calling a Service (just like
consuming an external web-service logically) that is an independent
transaction. So an ERROR Trap will need to be constructed, and then service
X_rollback would need to be called in the error handling...
Yes it adds much
Hi Robert,
Maybe, but the documentation does not say anything about this.
This would both limit and extend the use of servive-calls I guess.
In my case, when my service picks the next of several counters, it will
create holes in my counter-series. I guess I have to redesign...
Best
I have the same trouble with the error handler feature. I was so excited
when it was introduced but then realized it wasn't exactly what I wanted it
to be once I used it. It seems you still need many filter qualifications to
account for all of the different situations that will cause an error in
6 matches
Mail list logo
