We've noticed an issue with designs and customisations which has sent a few of us on a wild goose chase over the last few days.
Here's the scenario: You have a parse file, with a few customisations underneath it. In the parse file you have a design area, for this example we'll use a breadcrumb trail (asset_lineage). You customise that asset_lineage in one of the customisations because you want to change something, e.g. excluded asset types. You then go back and edit the parse file, changing something that you can't customise, e.g. levels_to_print. You think it's changed everywhere because you can't customise that value. However, the original value for levels_to_print has been saved in the customisation!
Two of us thought we were going mad with something not working, until we found this out.
Surely either everything should be customisable, or at least displayed as read only, or not stored behind the scenes like this at all?
[quote]We've noticed an issue with designs and customisations which has sent a few of us on a wild goose chase over the last few days.
Here's the scenario: You have a parse file, with a few customisations underneath it. In the parse file you have a design area, for this example we'll use a breadcrumb trail (asset_lineage). You customise that asset_lineage in one of the customisations because you want to change something, e.g. excluded asset types. You then go back and edit the parse file, changing something that you can't customise, e.g. levels_to_print. You think it's changed everywhere because you can't customise that value. However, the original value for levels_to_print has been saved in the customisation!
Two of us thought we were going mad with something not working, until we found this out.
Surely either everything should be customisable, or at least displayed as read only, or not stored behind the scenes like this at all?[/quote]
My understanding of this is that this is normal behavior. Design customizations are static settings that tweak your parse file, so any changes in your parse files, with the exception of deleting a design area, is not going to change your design customizations. To pick up parse file changes in your design customization, you have to delete the current customization and add a new one. That new one will pick up the parse file changes.