Cutom Business document tab's name changed after SP upgrade

[Former Member]

Hi Experts,

I urge for an urgent suggestion on one of main menu naming against an "user defined object (UDO)". We have a custom business document 'CSR' which is tagged to the main menu in Sourcing main work bench main menu (between home and project management). We are in process of upgrading our CLM system from SP2 to SP11.

While upgrading to SP11, though the custom business document 'CSR' features unchanged, the business document tab's main menu name changed from 'Request' to 'User defined' in Sourcing main work bench page. I am trying to understand to know where exactly we set the name for the main tab and how to bring back the name, which we lost after upgrade.

Please see below screen shots for more details.

Before SP upgrade the highlighted tab name was appearing as 'Requests'

After SP upgrade the highlighted tab name has changed from 'Requests' to 'User Defined'

I appreciate your quick response. Just in case if any further details required, please advice.

With regards,

Prabhakar

[former_member89217 · Accepted solution]

It is very possible that the localized resource that was used for this label was not implemented properly.  If the Deafult value was changed from User Defined to Requests. You would see as you do now. The proper way to override the localized resource is to provide an override value in the localized resource. Failing to do so will make the change. But the change will not persist past the next upgrade which will set the default value again. Have a look at that and let us know.

Regards,

Gary

[Former Member · Accepted solution]

I have checked in under localized resources. Since I am unsure it comes under which localized resource, manually checked randomly and identified relvent. Under one localized resource ID, the value 'Requests' found in 'Override value'. I mean the value 'Requests' is already in tact.

1) I have cleared value 'Requests', kept 'Override v'alue blank and saved localized resource ID

2) Reopened same localized resource ID, entered 'Requests' in 'Override value' and saved

I think the issue resolved by doing so. How ever, I would like to know the more optimized / best practice to handle this case. I appreciate if you could advice.

With regards,

Prabhakar

[Former Member · Accepted solution]

Just an update. Today I have followed same procedure in our production system, which I have described in my previous message. But this time it didn't work in our production system. I request to help.

[former_member89217 · Accepted solution]

Localized Resouces used in the UI are cached.  You can either use the cache refresh option in the application or restart the application.  However, after reading what you did to fix the problem before I'm not sure what you did there.  If there are multiple localized resources involved with customization, you need to be very sure which resource is being used to accomplish the customization. Further as I staed earlier, the ovveride value not the default value need to be changed if you want a change that will persist across an upgrade.