We use in most of our projects multiple master templates integration into a target template for the target database.
So e.g. we have Template A and Template B combining some elements of A and B together in Template C for Target Database DBc.
All is working fine exept from $Actions, if we create new shared actions in A we have to transfer them manually to Template C.
I detected now that there is another problem concerning view column property, tab sorting, checkmark "Click on Column header to sort “Change to View”.
You have to choose a view in this case, there is no formula for view alias possible to enter.
If I take 2 views in A, link them in a circular way and apply template refresh on C, one view is not working. If I click on the view header I will get “Object had been deleted”.
This is, because on update the old view infomation is replaced, and the first view updated in the template is the one not working.
When will Lotus stop to “help” designers with list boxes to select something wich will result in a internal document id and you do not have any chance to get the thing working?
There are so many view links, think of embedded views, where internally the view alias is stored, and a change of a view name will not cause any trouble and all is working fine. Why do Lotus do the internal resolving of a view link in this case in a special way?
Ilja
