Invalid 'Field Label' record even though the selected outside Table 'Risk' is allowed.

[timcalvert]

Hi,

I am getting the following error message when trying to create a field label for a field in an extended table:

Invalid 'Field Label' record even though the selected outside Table 'Risk' is allowed.

The field is called name.

The extended table is sn_risk_risk

It extends table sn_grc_item

The field currently has a label of 'Name'. I just want to change this to 'Risk name', but only for the Risk table sn_risk_risk, not the base table it is extended from.

Any ideas anyone?

I know I can use a script to change this on the form, but this is not the solution I am looking for, and neither is changing the label at the base table level.

Thanks.

Tim

[timcalvert]

Thanks for the reply Shahid.

Please see attached screen shots and logs captured

[Shahed Shah1 · Accepted solution]

I was unable to reproduce the exact issue, but was able to lookup the message and identify that it is related to application scoping within the platform. While the sn_risk_risk table extends the sn_grc_item table, it actually belongs to another application scope - Risk. So there would be some cross-scope privileges and I suspect this is the cause of the message.

Doing a quick test I was able to create a label for the name field on the sn_risk_risk table, by:

1. Navigating to a form on the table (e.g. Risk > Risk Register > All Risks then select a record)
2. Switching the Application Scope to "Risk".
3. Right-click on the name field and select Configure Dictionary (the sn_risk_risk table name will be populated for you)
4. Scroll down to the Labels related list and click New.
5. Enter the desired label and plural label then click Submit.
6. Navigate back to the form you will observe that the field takes on the new label

Quick notes:

• When I performed the above steps, while in the GRC Profiles scope, the New button (UI Action) does not appear on the Labels related list
• I did attempt to create a new record in the sys_documentation table directly in the GRC Profiles scope, and observed that sn_risk_risk table was not available for selection

Of course, the steps can vary, but I hope this sets you in the right direction

[timcalvert]

Hi Shahid,

Thanks a lot!

That appears to work. I guess I was trying to keep everything in the same update set, but it is not possible due to the different application scopes.

So when I implement into PROD, I will need to transfer 2 updates, for the different scopes.

kind regards

Tim