I’ve created a template called Shared Code that contains some script libraries, views and forms that I typically include in other templates. When I paste design elements from Shared Code into another template, I choose to have the pasted design elements inherit from the Shared Code template. These pasted design elements have “Shared Code” specified as the design template name, and also have a special icon to the left of their design name in Domino Designer.
The above is all working as I expected. However, when I refresh the design of a database (NSF) with a template that includes design elements that inherit from Shared Code, the design elements from Shared Code in the database (NSF) do not have “Shared Code” specified as the design template name and the special icon no longer appears.
The problem I have with this behavior is that when I need to roll out a change to a design element in Shared Code, I need to put all of my application templates on my production servers, instead of just the Shared Code template.
My question is, has this behavior changed between R5 and ND6? Or, is this behavior a result of a bug in the ND6 codestream that has been fixed in later codestreams?
Subject: Inherit from the design template question
Try pasting your ‘shared code’ template design elements into the main template and letting them inherit there instead.
When you change anything in sharedcode.ntf, you first refresh the design of the main.ntf to pick up the changes in sharedcode.ntf and then use the main.ntf to refresh the design of the main.nsf.
Not sure if the behaviour you are describing always happened or not…
Subject: Thanks for responding! Here are my responses…
Try pasting your ‘shared code’ template design elements into the main template and letting them inherit there instead.
I’m doing that already.
When you change anything in sharedcode.ntf, you first refresh the design of the main.ntf to pick up the changes in sharedcode.ntf and then use the main.ntf to refresh the design of the main.nsf.
I can do a build of the main.ntf before refreshing main.nsf. However, if I have 100 templates that inherit some design elements from sharedcode.ntf, and I change something in sharedcode.ntf, I need to build all 100 templates again in order to deploy the change across all 100 databases. Either that, or I need to keep sharedcode.ntf and all 100 templates on my prod server, and do a Load Design. This is my issue. I thought I wouldn’t need to keep all templates on my server in order to have a design change in sharedcode.ntf propogate throughout all 100 databases.
Subject: RE: Thanks for responding! Here are my responses…
100 templates is a fair few!
Do you keep your templates in the root of data or in a sub-directory? If you put them into a sub-directory you can then do a l design , to run the design task on just that sub-directory. Suggest you consider placing all templates that inherit from shoredcode.ntf into one folder to allow you to update them in one hit…