cancel
Showing results for 
Search instead for 
Did you mean: 

Disable Dinamic Models configuration

agey
Champ in-the-making
Champ in-the-making
Hi all,

My model, customModel.xml, is enabled as a Dynamic Model. I tried to change customModel.xml to add "Multi Selection" metadata but it is not possible. It returned the error
Failed to validate model update - found non-incrementally updated TYPE
.

I have been trying to disable a "Dynamic Models" configuration and seems that I've finally found how.

I would like to discuss it with you if in this way, data could be lost (though apparently not the case) and if there is another way to do it.

These are the steps:

1. Download the web-client-config-custom.xml of Data Dictionary space and then, delete it from space. If exist other web-client-config-custom.xml files that use types and aspects defined in the Dynamic Model delete them too.
2. Reload in the Web Client Config Admin Console.
3. Update customModel.xml file in the folder "Data Dictionary" (Dynamic Model configuration) by another file, exampleModel.xml, with different uri and with types and aspects which are not being used in a file web-client-config-custom.xml
4. Disable Dynamic Model flag in the properties of file.
5. Delete the file.
6. Stop Alfresco
7. Modify custom-model-context.xml to add the path file customModel.xml in the folder shared/classes/alfresco/extension/.
8. Start Alfresco
9. Upload again the web-client-config-custom.xml to Data Dictionary space.
10. Reload in the Web Client Config Admin Console.

Now, the Dynamic Model configuration is disable and the metadata are defined in the customModel.xml in the folder shared/classes/alfresco/extension/. This metadata definition can be change and metadatas of contents are updated according to changes.

Is it a good way to do this? Do you see any problem in that?

Thanks a lot in advance
2 REPLIES 2

agey
Champ in-the-making
Champ in-the-making
Nobody wants to say about this topic? Nobody has tried to do it?
Please, I would like to know what you think about to disable the Dynamic Model configuration in this way. Is there another way?

blazer
Champ in-the-making
Champ in-the-making
Thanks, this worked for me!

had a similar problem where a new version of our document model (only one property / aspect added) did not work as a dynamic model.
Replacing with updated version did not work, delete did not work, but replacing with a very simple model did the trick. Without this I could not "switch" to the filesystem-model. The same model that could not be replaced as a dynamic model worked perfectly as a static model.