nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

As we transition to the new Hyland Community, some post links may be temporarily disrupted as we finalize redirects. We apologize for the inconvenience and are working to resolve this as quickly as possible. Details.

Alfresco Upgrade - Problem with old aspect

tatatanja

Hello!

We haved upgraded Alfresco Community from 4.2c to 5.0d.
We used the AddOn FME Datalist Extension (fme-alfresco-extdl) at Alfresco 4.2c. Now at 5.0d we didn't install the Datalist Extension and so we have some problems with old datalistitems in Share with following Exception:

2016-02-12 09:48:37,293  ERROR [scripts.forms.FormUIGet] [ajp-apr-8009-exec-1] org.alfresco.service.cmr.dictionary.DictionaryException: 01122050 Failed to create anonymous type as specified aspect {http://www.alfresco.org/model/datalist/1.0}dataListItemId not found
‍‍‍

I am not able to remove the aspects of all Items with Javascript and I am not able to extend the existing datalistModel.

Can anyone help me?

Regards
Tanja

Find more posts tagged with

Comments

afaust

Hello,

unfortunately, removing an addon is not as simple as adding one.
In this case you have various options:
- (quick&dirty) simply upload the model XML from the FME data list extension addon into the Data Dictionary / Models directory - this re-enables the FME model without requiring the full addon and all existing aspects should work again
- (clean) bootstrap the model XML from the FME data list extension via a custom Spring bean in the tomcat/shared/classes/alfresco/extension directory - this will reenable the model the same as the item above, but allow you to simply remove the custom Spring bean and model again at a later time (the quick&dirty variant means that you may never be able to remove the model again unless you eliminate or clean up all nodes that use that model)
- (quick&extremely dirty, but no need to keep FME model around) remove all the FME data list extension aspects from all nodes via a DB statement - be careful not to delete too much (note that this will also affect any versioned nodes with FME data list extension aspects)

Regards
Axel