cancel
Showing results for 
Search instead for 
Did you mean: 

Hiding the rows or disabling the Opportunity ID link in the Opportunity OWL screen based on the Logged In User

former_member187149
Participant
0 Kudos

Hi Community,

In the opportunity business object I have an Indicator field under an EC.If that indicator is set then that particular opportunity should not be visible or editable in the opportunity OWL to all the Employees other than the Owner of the Opportunity and two other Employees(these two employees are generic for all the opportunities).

How should I achieve this requirement.Kindly share your thoughts on it.I tried to add an UI switch to the OWL but that is allowing me to only restrict the

visibility property of the column.But I need read only property for rows.

Regards,

Navin

Accepted Solutions (0)

Answers (2)

Answers (2)

former_member187149
Participant
0 Kudos

Hi Pradeep/Sunil

Any suggestion on the above scenario.

HorstSchaude
Product and Topic Expert
Product and Topic Expert
0 Kudos

Hello Navin,

Did you check if the Access Control within the Opportunity can help you here?

Bye,

   Horst

former_member187149
Participant
0 Kudos

Hi Horst,

Thanks for your response.Could you please provide an example or document on this.

Regards,

Navin

HorstSchaude
Product and Topic Expert
Product and Topic Expert
0 Kudos

Hello Navin,

I suggest to start with

HTH,

   Horst

former_member187149
Participant
0 Kudos

Hi Horst,

I have gone through this blog but it deals with the creation of restriction for the custom objects.

But my scenario is to restrict the read and write access for Opportunity instances to the users who are not the owners of it.

Regards,

Navin

HorstSchaude
Product and Topic Expert
Product and Topic Expert
0 Kudos

Hello Navin,

To phrase it in my words:

     Erverybody shall see the data, but only some should be able to modify it.´

Because on top it was "hiding" which is achieved by an ACL.

Bye,

   Horst

former_member187149
Participant
0 Kudos

Hi Horst,

This is what my requirement too.I am aware about using ACL for custom business objects by inheriting standard Access contexts.But in my case I need to carry out the restrictions for the instances of standard BO which is opportunity.What is the approach should I need to follow for standard BOs to achieve instance based access restrictions.

Regards,

Navin

HorstSchaude
Product and Topic Expert
Product and Topic Expert
0 Kudos

Hello Navin,

If the ACL of opportunity does not contain the context you need, then ACL is not the solution here.

Sorry,

    Horst

former_member187149
Participant
0 Kudos

Hi Horst,

Thanks for your responses Horst.

Regards,

Navin