You need to sign in to do that
Don't have an account?
Mike A Smith
How do I restrict a picklist option after the record is created?
Hi,
I have a formula working to restrict 2 picklist options (Feature , Enhancement) to most users but does allow them to select a Third option (Fix) when creating a NEW record. Can I add something to the same VR to then prevent the users from editing the record and selcting either 'Feature' or Enhancement'? Below is the piece of the VR that would prevent Dale Doback from selecting 'Feature' or 'Enhancement' when creating the record but Dale CAN save the new record with 'Fix' selected. But Dale is then able to edit the PL on the NEW record he created and change 'Fix' to either 'Feature' or 'Enhancement'.(but should not be able to do that) what can I add to the VR to prevent him from doing that edit and selecting either of those 2 PL options ? (In other words Dale is only ever able to set 'FIX' in the configuration request type...he should never be able to select 'Feature' or 'enhancement')
AND(
ISNEW(),
OR(ISPICKVAL(Configuration_Request_Type__c,'Feature'), ISPICKVAL(Configuration_Request_Type__c,'Enhancement')),
OR($User.Id !="005d000000xxxxxx", /*John Doe*/
Thanks.
I have a formula working to restrict 2 picklist options (Feature , Enhancement) to most users but does allow them to select a Third option (Fix) when creating a NEW record. Can I add something to the same VR to then prevent the users from editing the record and selcting either 'Feature' or Enhancement'? Below is the piece of the VR that would prevent Dale Doback from selecting 'Feature' or 'Enhancement' when creating the record but Dale CAN save the new record with 'Fix' selected. But Dale is then able to edit the PL on the NEW record he created and change 'Fix' to either 'Feature' or 'Enhancement'.(but should not be able to do that) what can I add to the VR to prevent him from doing that edit and selecting either of those 2 PL options ? (In other words Dale is only ever able to set 'FIX' in the configuration request type...he should never be able to select 'Feature' or 'enhancement')
AND(
ISNEW(),
OR(ISPICKVAL(Configuration_Request_Type__c,'Feature'), ISPICKVAL(Configuration_Request_Type__c,'Enhancement')),
OR($User.Id !="005d000000xxxxxx", /*John Doe*/
Thanks.
You can try below validation rule.
Please mark as Best Answer if above information was helpful.
Thanks,
Sorry, I thought you haven't posted full validation rule, Have updated now can you check.
Thanks,
Can you check above?
Thanks,
Here's an updated version of the validation rule:
AND( ISCHANGED(Configuration_Request_Type__c), NOT(ISNEW()), OR( ISPICKVAL(Configuration_Request_Type__c, 'Feature'), ISPICKVAL(Configuration_Request_Type__c, 'Enhancement') ), $User.Id = "Dale's User ID" )
Replace "Dale's User ID" with the actual User ID of Dale Doback. This condition ensures that if the Configuration Request Type field is changed and the new value is either 'Feature' or 'Enhancement', it will only trigger the validation rule if the user editing the record is Dale Doback. This will prevent Dale from selecting those options once the record has been created with 'Fix' selected. If you need more updates this https://dailysportsupdates.com/ platform is very updated and informative must explore it.