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

timcalvert · ‎08-24-2017

Hi,

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

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

Shahed Shah1 · ‎08-30-2017

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:

Navigating to a form on the table (e.g. Risk > Risk Register > All Risks then select a record)
Switching the Application Scope to "Risk".
Right-click on the name field and select Configure Dictionary (the sn_risk_risk table name will be populated for you)
Scroll down to the Labels related list and click New.
Enter the desired label and plural label then click Submit.
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

View solution in original post

Shahed Shah1 · ‎08-25-2017

Hi Tim

How are you trying to create a field label? Keeping in mind that this table is in the GRC Applications scope, field labels are stored in the sys_documentation table. So you can go into that table and create a record with the necessary values:

Table=sn_risk_risk

Element=name

Language=en (or other language that you're interested in)

Label=(the label you want)

Plural=(based on the desired label)

Hint=(optional)

Or is this the method you used that's not working?

Regards

Shahid

gupta_vipul013 · ‎08-25-2017

Hi Tim,

Yes, there is an OOTB solution to update the Column label in the child label. Follow the below points to achieve the same:

1. Configure Field Dictionary.

2. There is an Related list - Labels. Click on the New button on this related list.

3. Add a new label for the child table and click on save.

This will update only the label of the child table, no impact on the base table.

Please let me know, if you face any challenge in the same.

Regards,

Vipul

timcalvert · ‎08-27-2017

Hi Shahid and Vipul,

Yes, I have tried both of those methods, and that is where I am getting the error message from.

I have been able to re-label a child table field via those methods before, which is why I posted. I have not seen that error message before. Searching the Hi Portal and community did not yield any results.

Thanks.

Tim

Shahed Shah1 · ‎08-29-2017

Thanks for confirming your steps to try get the labels created. I've not seen this error before.

Can I ask you two things:

A screenshot of the error (to help a bit more with context)
Enable session debug by navigating to System Diagnostics > Session Debug and selecting any one or a combination of the modules within this group.
1. My usual combination is SQL (Debug), Business Rule and Log. It may also be prudent to include Security.
2. When you reproduce the issue scroll down past the form and you will see a whole bunch of colour-coded statements.
3. Please copy this and share it here. (Probably best as an attachment in case the debug output is huge)
An alternative way to get the debug: Navigate to System Applications > Applications, click on the title of the application (in this case GRC Applications) scroll down to the related links and click on Enable Session Debug.
1. You may not always get the application listed here to select, so Step 2 is the usual route (for me at least).

I'm hoping that the session debug will reveal some clues to troubleshoot. If you rather that we work on this together, feel free to ping me directly.