topic Changing dynamic models? in Alfresco Archive https://connect.hyland.com/t5/alfresco-archive/changing-dynamic-models/m-p/208957#M162087 <HTML><HEAD></HEAD><BODY><SPAN>I'm prototyping a solution and thought I would take advantage of dynamic models to avoid continuous server restarting while I develop and debug my content model.</SPAN><BR /><BR /><SPAN>However I've found that even the simplest change to a model is triggering errors when I try to save it where Alfresco claims the model is invalid because it "found non-incrementally updated TYPE".&nbsp; Here's a sample exception snippet:</SPAN><BR /><BR /><SPAN>02:30:28,587 ERROR [org.alfresco.webdav.protocol] Internal Server Error: </SPAN><BR /><SPAN>org.alfresco.error.AlfrescoRuntimeException: Failed to validate model update - found non-incrementally updated TYPE '{my.new.model}sop'</SPAN><BR /><SPAN>&nbsp;&nbsp;&nbsp;at org.alfresco.repo.dictionary.DictionaryDAOImpl.validateModel(DictionaryDAOImpl.java:1192)</SPAN><BR /><SPAN>&nbsp;&nbsp;&nbsp;at org.alfresco.repo.dictionary.DictionaryModelType$DictionaryModelTypeTransactionListener$1.doWork(DictionaryModelType.java:465)</SPAN><BR /><SPAN>&nbsp;&nbsp;&nbsp;at org.alfresco.repo.security.authentication.AuthenticationUtil.runAs(AuthenticationUtil.java:437)</SPAN><BR /><BR /><SPAN>As an example of what caused this I used the standard example model with the my:sop type - everything works fine until I tried to make one of the SOP type properties mandatory so that the meta-data property sheet would require it of new documents.&nbsp; Specifically I tried changing:</SPAN><BR /><BR /><SPAN>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;properties&gt;</SPAN><BR /><SPAN>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;property name="my<img id="smileytongue" class="emoticon emoticon-smileytongue" src="https://connect.hyland.com/i/smilies/16x16_smiley-tongue.png" alt="Smiley Tongue" title="Smiley Tongue" />ublishedDate"&gt;</SPAN><BR /><SPAN>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;type&gt;d:datetime&lt;/type&gt;</SPAN><BR /><SPAN>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;/property&gt;</SPAN><BR /><BR /><SPAN>to</SPAN><BR /><BR /><SPAN>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;properties&gt;</SPAN><BR /><SPAN>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;property name="my<img id="smileytongue" class="emoticon emoticon-smileytongue" src="https://connect.hyland.com/i/smilies/16x16_smiley-tongue.png" alt="Smiley Tongue" title="Smiley Tongue" />ublishedDate"&gt;</SPAN><BR /><SPAN>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;type&gt;d:datetime&lt;/type&gt;</SPAN><BR /><SPAN>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;mandatory enforced="true"&gt;true&lt;/mandatory&gt;</SPAN><BR /><SPAN>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;/property&gt;</SPAN><BR /><BR /><SPAN>which triggered the above exception.&nbsp; Now if I make the mandatory element say false (both the attribute and value part - its not clear why we need both or what the distinction) then I can save.&nbsp; But as soon as I try to make them true again I get the exception all over.</SPAN><BR /><BR /><SPAN>I thought it might be because I already had some content without the publisedDate set - so I set the date and saved that document then treid the model change again.&nbsp; No such luck.&nbsp; Then I thought maybe I should be making the model inactive while I make the change but it wont let you inactivate a model that you instances of kicking around. </SPAN><BR /><BR /><SPAN>Am I up against a bug, a genuine restriction (which seems pretty darned limiting!) or is there some other way to change the model like this?</SPAN><BR /><BR /><SPAN>EDIT: Adding additional info…</SPAN><BR /><BR /><SPAN>I've verified this is nothing to do with content using the model already existing - I added a new model and got the same problem without creating any docs using it as their content type.&nbsp; I was also able to create a model where one parameter already had a mandatory =&gt; true element.&nbsp; When I did that I could set the value to false or delete the mandatory element,&nbsp; but once I did I couldn't put it back.&nbsp; An parameter that already had a mandatory =&gt; false element when the model was added wouldn't let me set it to true.&nbsp; So it seems like the checking lets you relax the constraints but not increase them. </SPAN><BR /><BR /><SPAN>I also found I could add parameters to my models content types but could not remove them - even if no content used them yet.&nbsp; </SPAN><BR /><BR /><SPAN>I'm pretty sure these restrictions do not apply when you do not use dynamic models - you just edit the files in the classes/alfresco/extensions dir and restart the server.&nbsp; In that case am I risking breaking something further down the line?&nbsp; I know the docs warn of breaking your repository with model changes and being ready to throw stuff away until you've done with content model definition but surely non-conflicting changes (at least in respect to existing content) like this should be possible?&nbsp; I would love to know if there is a flag to disable some of these checks when using dynamic models - or at least get warning instead of errors - and how to set it.</SPAN></BODY></HTML> Thu, 29 Jan 2009 10:58:13 GMT moschops 2009-01-29T10:58:13Z Changing dynamic models? https://connect.hyland.com/t5/alfresco-archive/changing-dynamic-models/m-p/208957#M162087 I'm prototyping a solution and thought I would take advantage of dynamic models to avoid continuous server restarting while I develop and debug my content model.However I've found that even the simplest change to a model is triggering errors when I try to save it where Alfresco claims the model is i Thu, 29 Jan 2009 10:58:13 GMT https://connect.hyland.com/t5/alfresco-archive/changing-dynamic-models/m-p/208957#M162087 moschops 2009-01-29T10:58:13Z Re: Changing dynamic models? https://connect.hyland.com/t5/alfresco-archive/changing-dynamic-models/m-p/208958#M162088 <HTML><HEAD></HEAD><BODY><SPAN>I have encountered this same problem.</SPAN><BR /><BR /><SPAN>How can it be avoided?</SPAN></BODY></HTML> Fri, 06 Feb 2009 02:04:09 GMT https://connect.hyland.com/t5/alfresco-archive/changing-dynamic-models/m-p/208958#M162088 slothrop 2009-02-06T02:04:09Z Re: Changing dynamic models? https://connect.hyland.com/t5/alfresco-archive/changing-dynamic-models/m-p/208959#M162089 <HTML><HEAD></HEAD><BODY><SPAN>My solution was to spend more time on design of the model up front so it doesn't change, and stop using any of the dynamic features except for ui customization.&nbsp; Its a shame because prototyping is definitely a time when you don't want to be starting and resatarting the server.&nbsp; Also you definitely don't want to add much content at all (unless you have an automated process to do it) until you have really nailed own your model.&nbsp; </SPAN><BR /><BR /><SPAN>In theory alfresco could add modelling level ui features and tools to make it easier tto migrate data between content models, but for now I think its not a priority - you'll just have to write your own scripts.&nbsp; That's assuming you can even change the model at all, which you can't.&nbsp; If you want to look at the source code it is pretty obvious what to change to sidetrack this constraint check…</SPAN><BR /><BR /><SPAN>My theory is that experienced alfresco users and content management designers don't need this flexibility anyway. So really having the model in the ui for anything other than reference is a gimmick to them.</SPAN></BODY></HTML> Fri, 06 Feb 2009 02:35:16 GMT https://connect.hyland.com/t5/alfresco-archive/changing-dynamic-models/m-p/208959#M162089 moschops 2009-02-06T02:35:16Z