"computed for display" fields creating problems

Hi,

We are in the process of renaming the server from L2/Server/RST to L2/Server/WXY. While doing so , we have to check for the Hard coded names for the server in the design of our applications.

One of the application has a Shared and computed field called “server name” and contains the hard coded name of the old server.

We changed the default value of this field to the new server name.

There are other “Computed for Display” Shared fields in the Database that has DbLookup running in them. This DBLookup uses the Shared field “server name” as its parameter.

Ideally , when we should open a document these “Computed For Display” fields should be able to lookup values from the new server now.

However , when we open a document , it gives an error : “Unable to find path to the server”, as it try to search the old server.

I do not understand that why the “computed for display” fields are NOT being recalculated and hence NOT taking the new server name as the paramater in their DbLookups.

Any insight into this would be really helpful.

Thanks,

Meggie.

Subject: “computed for display” fields creating problems

Hi Meggie,

The computed for display fields are being recalculated.

However, the computed field is NOT being recalculated when you open a document. It won’t be recalculated until you save the document. So when you open a document, the old server value is used.

You’ll have to write an agent to set the field Servername with the correct value for all existing documents.

Another thing: make the field computed for display. There’s no reason to store the same value in every document.

(in this case: run an agent to delete the field servername in existing documents; even if you make the field computed for display, it will still be there in existing documents and use its value (until you save the doc))

Regards,

René