Report Attribute – MultiObjects
This attribute MultiObjects is required to be specified in case multiple objects of the same collection are being added/modified in a Report. It is required specifically in case of multi master creation or alteration.
Currently, if multiple external data objects are selected for creating vouchers, the system processes them one by one. If it encounters an error while processing any object, it stops and shows the report with an error message. Objects created before the error remain, while the remaining ones are not processed.
The new requirement is to allow skipping objects with errors and continue processing the others without showing an error message.
Syntax
MultiObjects: <Collection Name>: <Logical Expression>
Where,
<Collection Name> is the name of the Collection for which modifications are to be done.
and
<Logical Expression> here means Yes/No.
Example
MultiObjects : TSPL MO Stk Collection : Yes
So here in case there is an error while creating TSPL MO Stk Collection then the error will be skipped and the other collection will be created
-
Existing Behavior:
By default, the system will follow the current behavior of stopping at the first error. -
New Behavior:
The new “skip errors and continue” behavior will be enabled only when explicitly instructed by the application.
Difference Between Previous and Updated MultiObjects Attribute Usage
Scenario | Previous Capability | Updated Capability |
Single Collection | Multiobjects:Coll1 | MultiObjects: Coll1 : Yes |
Multiple Collections (Single Line) | MultiObjects: Coll1, Coll2 | MultiObjects: Coll1, Coll2 : Yes |
Multiple Collections (Separate Lines |
MultiObjects: Coll1 MultiObjects: Coll2 |
MultiObjects: Coll1: Yes MultiObjects: Coll2: Yes |
Error Handling | Not supported (Errors stop execution). | MultiObjects: Coll1 : Yes (enables skipping errors) |
Multiobjects:Coll1 |
Backward Compatibility:
- Existing configurations (without the second parameter) will continue to work as before. Collections can still be specified using a comma-separated list in the first parameter
Key Takeaways for Developers:
- Add the optional second parameter (Yes/No) only when enabling skip errors.
- Without the second parameter, the system defaults to current behavior.
- Ensure the report processes all valid objects and skips errors only when explicitly instructed.