This question is locked. New answers and comments are not allowed.
When I update the model from database (Oracle 11g) I get the following message:
An unexpected exception has occured. The exception message is:
'Cannot add item with key 'MetaStoredProcedureParameter'TOROL'.KIMENO' to MetaItemIndex.'.
I get this message regardless of what I selected to update in the dialog. The culprit seems to be a group of stored procedures with identical names and signatures but in different packages. This is actually a valid setup. When I temporarily remove theese from the model xml, everything works, when I reintroduce them, everything breaks.
It seems OA uses only the short procedure name to identify model artifacts whereas it should use the package-qualified name. The same problem can be observed in the update from database UI and the model schema explorer where I can only see the short procedure name, not the containing package so I'm left with dozens of identical named entries.
The problem is only present when the procs are already part of the model when updating, not when I initially add them, but it's highly contraproductive to always remove then add them on every model update or sort out which is the one from the identical entries that I actually need. Otherwise I can map them to domain methods and use them normally, so this is mostly a designer issue.
An unexpected exception has occured. The exception message is:
'Cannot add item with key 'MetaStoredProcedureParameter'TOROL'.KIMENO' to MetaItemIndex.'.
I get this message regardless of what I selected to update in the dialog. The culprit seems to be a group of stored procedures with identical names and signatures but in different packages. This is actually a valid setup. When I temporarily remove theese from the model xml, everything works, when I reintroduce them, everything breaks.
It seems OA uses only the short procedure name to identify model artifacts whereas it should use the package-qualified name. The same problem can be observed in the update from database UI and the model schema explorer where I can only see the short procedure name, not the containing package so I'm left with dozens of identical named entries.
The problem is only present when the procs are already part of the model when updating, not when I initially add them, but it's highly contraproductive to always remove then add them on every model update or sort out which is the one from the identical entries that I actually need. Otherwise I can map them to domain methods and use them normally, so this is mostly a designer issue.