Hi Hanu,
thank you for your reply.
Your suggestion is an alternative but as you mentioned, doesn't really solve the problem:
- If the user doesn't recognize the warning message, the "Instance with the same key already exists" error will still come up on the next time he/she will hit "Save"
- Additionally, as the bottom-message-line only shows one message at once if you don't click to see all, the warning message will probably replace another message on any change the user is making (AfterModify), allthough my message is probably not relevant concerning the current user interaction
So if it is not possible at all to get a real solution here, SAP development should think about an alternative procedure here, e.g. to execute custom "ValidationOnSave"-events in xbo-Files before the standard-"BeforeSave" event.
The routine would then be: XBO-BeforeSave, XBO-ValidationOnSave, Standard-BeforeSave-Standard-ValidationOnSave. Otherwise there needs to be another internal mechanism to create IDs / check for duplicates.
Kind Regards
Pablo