Nested Queues with a Detail Page (2013)

I think what is happening is a bug that we’ve just fixed but haven’t released. When you change a model id - it did not automatically crawl your page to find references to that model id within page components and model conditions. So things broke.

And most frustratingly - somtimes in the properties for a component - the model value would show the new name (just in the drop down) but the saved field would not be correct. So you’d never know.

There are two ways to fix this.

  1. Go into your XML and copy the new modelId to all the places where the old id was found.

  2. Go to all the components and in the model property, select a different model and then go back and select the correct (new) model. This forces the synch to the new name. Sometimes you have to create a dummy model just so you have another one to choose.

Irritating, I know… And fixed - but not yet released…

If this doesn’t work, or you are just throwing your hands up in despair, we can look at your page if you give us login access.

(originally posted Dec 13th, 2013)