0

I'm looking to give specific user access to edit single custom field on 'Opportunity Product'. This user should not have the ability to edit any 'Opportunity' field.

I created ‘Opportunity Product’ validation rule which yields if the user change any forbidden field and I had to create ‘Opportunity’ validation rule (prevent any opportunity modification)

It seems like the 'Opportunity' and the 'Opportunity Product' both related to the same permission and when I try to edit this specific Opportunity Product field – the Opportunity validation rule yield.

And idea how to prevent this user edit opportunity but allow him edit this ‘Opportunity Product’ specific field?

The 'Opportunity Product’ validation rule:

AND (NOT (ISCHANGED ( my_custom_field__c )), $Profile.Name = 'Support & Automation')

And the 'Opportunity' validation rule:

$Profile.Name = 'Support & Automation'

Thanks!

  • can you paste the validation rule here? – rahul gawale Feb 18 '19 at 8:06
  • Hi ) added in the post – aralele Feb 18 '19 at 8:26
  • 1
    As you are using profile, you can change all fields on the opportunity as read-only for the profile 'Support & Automation' from field level security, and on Opportunity Product make fields which you want editable from field level security, in this case you won't need any validation – rahul gawale Feb 18 '19 at 9:06
  • 1
    True. I can, though I thought maybe there is more elegant solution. instead hovering each field one by one.. – aralele Feb 18 '19 at 10:54
0

Opportunity Product has a master-detail relationship to Opportunity, so it inherits its CRUD permissions from Opportunity. You won't be able to remove object-level Edit access to the Opportunity from a user who can edit the Opportunity Product (since it's Opportunity Edit that grants the latter permission), and that means that certain standard required fields cannot be marked as read-only for this user. That list includes Name, Stage, CloseDate, and a handful of others.

Opportunity Product has the same basic problem - any user who has permission to edit the object at the CRUD level also gets to edit the Opportunity, Product, Quantity, and Sale Price fields.

A validation rule can only take you so far. This rule, for example,

AND (NOT (ISCHANGED ( my_custom_field__c )), $Profile.Name = 'Support & Automation')

will allow a Support & Automation user to make any change to the Opportunity Product, provided that they also change my_custom_field__c.

This one:

$Profile.Name = 'Support & Automation'

means that you cannot have any automation that updates the Opportunity level from the Opportunity Product level (unless it's designed very carefully and excludes updates made by these users, which won't be possible in all cases), because the rule will then fire when the programmatic update goes off.

Unfortunately, I think the only thoroughgoing solution to this ask is code-based. You'd need to completely remove Edit permission for Opportunity and Opportunity Product for these users (at the CRUD level rather than FLS) and implement some type of custom UI for the users to initiate these updates, running automation or Apex that ignores CRUD and FLS to perform the changes.

| improve this answer | |
0

Well since the 'Opportunity' and 'Opportunity Product' sharing the same permissions and since I would rather avoid coding here - I took rahul gawale answer and added 'read only' to all 'Opportunity Product' fields (except that single field) + added the Opportunity validation rule.

| improve this answer | |

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.