Hi,
the MessageService add result might get rolled-back due to the DI Error raised in previous call atom6. I assume your chosen parameter "stop processing if fails" for atom6 is set to #false.
In these older B1i versions, there is a strict-two-phase commit, which might do the rollback in case of an erroneous DI call, but if you're working with a newer B1i version, you can switch towards "SAP Business One DI Single Transaction" via SCENARIOS -> Step Design. This setting will change the roll-back behavior of B1i: Every DI Call will be valid immediately and a roll-back is prevented.
An update to an actual B1i would be necessary.
Another option is to split the two processes:
- Scenario Step 1: Creation of object 18
- Scenario Step 2: Creation of the B1 internal Message handing over DI call result of step 1.
You can use the concept of "successor" step to combine both scenarios. Please check B1i Online Help for search tag "Predecessor Inbound".
Best regards
Bastian
P.S.: I always try to only have one add/update call via DI API per single scenario step.