I have a supertype model with an overview, where I have two sub type models.
For each subtype I load some test data into my local environment.
When I try to open the document, I get this error.
In the UAA rules, I disabled the creation of new documents for the subtypes.
Could this be the problem or do you have another idea?
We migrated from 2023.06-ext6 to 2024.06-ext3
hi @clara-fleet-yew,
that issue normally declares that you have no DataProvider in your application that is able to handle the data loading for current activity.
If you do not have a custom DataProvider for your form activity, then please check if your app model is correctly defining the Match Conditions for the current scene (descriptor of the default platformSingleDocumentDataProvidershould match this).
Here is an example (instance needs to be set):
In the UAA rules, I disabled the creation of new documents for the subtypes.
Since you are loading existing documents that should be no problem in here.
Hi @markus-agile-fog ,
the Match Conditions are already set like this. Before the update, it worked properly…
Do you have any other idea?
Regards
On close collaboration on finding the root cause @clara-fleet-yew and I found out that the issue has an project internal cause that became visible by changes in the canHandle... methods of PlatformSingleDocumentDataProvider against canHandle inPlatformSingleDocumentDataLoader.
In A12 2023.06 it was only checked against instance in descriptor whereas in A12 2024.06 it is also checked if a model of type form is available in the current scene (via ModelSelectors.modelDescriptorsByActivityId).
Since the project implemented a custom Overview Engine with custom EventHandlers the internal cause of the issue was a wrong modelId that was handed over via the action CRUDActions.selectRow({activityId, modelId, instanceId}).
Solution here is to receive the correct modelId for the clicked row of the overview. Since the allready available instanceId in regular A12 implementations is of pattern modelId/uuid it is possible to resolve the correct modelId from that.
