Problem when deploy a12 version 2024.06 ext6

Data Services
1

Hi, we are having a production env running with an old a12 version. The database doesn’t contain any documents since no one actually using it. But when update to version 2024 ext 6, we face the error

com.mgmtp.a12.dataservices.model.exception.DocumentModelDeSerializationException: Unable to deserialize model DnoContractCDM

with DnoContractCDM is a model deleted long ago. We were told to use Data Services Delete Model API to delete model from server, but that mean we have to go through all our database to check which model is no longer exist and to be deleted.
Do we have any other way to prevent this behavior, or call API delete for each of the model is the only way.
I would expect there is a way to reload model data every time the application start, so that the model in the database can be up to date with the resources

Thank you and best regards,

2

Hi @anh-quantum-quarry,
I think you can use this property configuration Full Model Import to delete all models stored in the database before reimporting the new ones.

3

Hi @thien-nimble-cursor, that sounds exactly like what we want to find right now. We will give it a try and let you know the result, thanks for the hint :wink:

4

Hi, me again.
It seems it doesn’t work as expected. I reproduced the problem locally and what I had done was:

  1. Start application at 2023 version with model named PartnerData, and no document was imported
  2. Remove PartnerData from models folder and Update to 2024 extension 6
  3. Put given key into yaml file
    image
    image1808×698 62.2 KB
  4. Start application again in debug mode. And then check cleanupPersistedModels function.
    image
    image2122×876 199 KB
    PartnerData is included in the list of entities to delete
    And when modelService.delete(e) trigger with PartnerData, an error is thrown:
    image
    image1827×958 152 KB
5

Hi @anh-quantum-quarry ,
Thank your your information,
This error comes from when deleting a model; we have a step to deserialize model JSON content. I think there’s some mismatch with your model content. Can you send me your PartnerData model?

6

PartnerData.json (23.1 KB)
Hi @dinh-sleek-chasm, thank you for your time. Here is the PartnerData model.

7

hi @anh-quantum-quarry
thank you, I’ll continue check this error.

8

Hi @anh-quantum-quarry,

This is indeed a bug that we will fix. We’ll keep you posted here once the fixes are released.
In additional @dinh-sleek-chasm guided you to a workaround. Was this functional for you?

Thanks for your patience!

9

Hi @svenja-still-dawn,
Yes, Dinh provided a solution for a fix while we were waiting for the release from a12, but after discussing with our team member, we agreed that cleaning the database is a proper solution. So we’re good for now.

Thank you for your time,
Anh

10

Update: This issue has been fixed in 2024.06-ext7 (A12S-6181) and 2025.06-ext2.