Hello everyone,
I have a question of understanding regarding the DB Design Refresh:
Our scenario:
We have development, test & demo and production server. The application is developed on the development server and gets a name as mastertemplate MT1. On the test & demo server a file is also created and it points to MT1 from where it should inherit the design. It itself is also a master template MT2 from which the production servers APP receives its design. MT1 -> MT2 -> APP
Now we have the situation that an agent which was written in MT1 in 2020 by developer A got changed by a developer B in MT2 (not MT1) at the end of 2023. This was also transferred to the production server´s APP. But now it turned out, that this change was not really good and it should be set back to the old state. So as we still ha the MT1 untouched, we refreshed MT2´s design with it.
But whenever we now perform a design refresh from MT1 to MT2, the agent in MT2 remains unchanged.
Our question:
Is it possible that the date has a higher relevance than the MT1 template during the design refresh and therefore an older design object from MT1 cannot overwrite a newer one in MT2? Or is there a time limit or... ? Or could it be that the MT1 agent is corrupt or the MT2 one ? No, "prohibit design refresh" was our 1. idea. Its definitely not set ! ;-)
Note:
We always save all self-written applications in NSF files and never in NTF files as its easier to handle them (i.e. subdirs )
Sincerly,
Jochen "Joe" Herrmann
We use Notes/Domino 12.0.1 and above. 32 bit only on 64 bit OS