cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

Restrict MDF field visibility based on permission group

duartecaixado
Explorer
0 Kudos
4,982

Dear community,

I need to restrict a MDF field visibility (in the Payment Information object) based on a permission group.

In this portlet we have two types of cards (main and meal card) and we want to allow employees to change their card number, but only if the Payment Method is Meal Card. On the other hand, the ones with the HR role can edit both card numbers.

Since this is a MDF it's been a challenge: I cannot restrict the visibility using a Business Rule (like described in https://blogs.sap.com/2018/01/12/restrict-visibility-of-field-date-of-death-in-employee-central/) because the field visibility is not possible to select (the base object is not "model").

I tried later on to create this rule using the Manage Configuration UI screen but I cannot restrict the visibility based on login user or permission group.

Have you faced something similar? How would you advise to proceed in order to make a field view only or not visible only for the login user/worker?

Thank you in advance for your thoughts.

Duarte

Accepted Solutions (0)

Answers (1)

Answers (1)

nlgro02343
Active Contributor
0 Kudos

Did you consider to remove visiblity or edibility by default via the config ui and instruct admins that, if they want to make changes) to use manage data instead? Regular employees shouldn't be able to access manage data anyway and this may be the easiest way to get the desired result (maybe good to add fields like user id, or name as search options on the object to make searching in manage data easier).

duartecaixado
Explorer
0 Kudos

Hi Jasper, thanks for looking at this topic. That would not work because we want employees to edit this portlet. We have two card numbers (Salary and Meal Card) but employees cannot change meal card number, only the salary one.

Since employees usually have the two cards in the same portlet, the error message is displayed for both types of cards.

This is the rule we designed but it is not working: paymentrule.png

Thank you again,

Duarte