When I change the LotusScript in an Action Button on a View, or even if I change the title on a Column in a View, and then Save the view, the Rebuilding Index message appears.
Why does the Index need Rebuilding after such changes?
I tried on another PC and this did not happen - so it appears that the view is not corrupt.
Is there a setting on the Client or in Designer to stop these time wasting Index Rebuilds?
As the view is fairly large this is costing me a lot of wasted time.
Subject: No formula changes made
I made no changes to docs that would be selected, nor to the content of the view other than cosmetic stuff - a column header or a column width or a number format change.
This has never cause a rebuild of the index in Designer in the past.
IBM - this is a “BUG” and is wasting my development time as I have to wait for the rebuilds to finish.
Subject: It could be more serious than that…
I haven’t attempted to reproduce this myself, but if so, it could be a much bigger problem than simply costing a developer’s time.
If you’re working on a view in a template that gets pushed to production, the subsequent design update (“Load Design”) could cause thousands of databases to require views to be rebuilt.
Subject: You can set it in the View design.
In your views properties (View infobox) you can specify when the view should be rebuilt. If you are testing and not working on a production environment then you can set the refresh to “Manual” until your happy with the design.
You can also set sortable columns to index on first use to save time on the NIF updating.
Subject: Action Button change to LSScript
I’ve just changed the LSScript code of an Action Button in a view and when I save the view the “Rebuilding Index” happened.
It has happened on other Db’s so I don’t think it’s a DB corruption. But it doesn’t happen in all cases of Action Button changes.
Definite BUG!!
Subject: It used to be this way, but I have not seen it recently.
In older versions of Notes (R4 ?) and changes to a view would force a rebuild. But now-a-days, the only changes that should do that are to the Selection, or a view column formula.
One thing to check. When you are changing the Column Title, is the “Programmable Use: Name” (Last tab on the column properties) also getting changed ? That may force a rebuild, as other column formulas could be using that value.
I’ve no idea why a Action Change would need to rebuild the index though.