Skip to main content
Hi All

 

Wondering if I can get some help with an issue that I am encountering.

 

1. I have a Validation Rule that prevents Users from changing the Stage of a Closed Won Opportunity but allows Sys and Data Admins to bypass (see below)

AND(

(OR (TEXT(PRIORVALUE(StageName)) = "Closed Won",

TEXT(PRIORVALUE(StageName)) = "Closed Won Renewal")),

NOT(OR(

$Profile.Name = "System Administrator",

$Profile.Name = "Data Administrator"))

)

 

2. There is a field on the Opportunity called 'ACV GBP' that is populated using Process Builder to give a Value in a certain currency. This is fired all the time without any critera and works as intended. (See Screenshot)

 

Validation Rule and Process Builder Flow error - Validation Rule firing when trying to Close Opportunity

 

3. Now the issue that I am running into is that for some Opportunities, I am getting an error message saying that the Opportunity cannot be Closed Won because the Validation Rule quoted is firing and preventing the Opportunity from Closing. (See Screenshot)

 

User-added image

 

 

Why is this happening and is there a way to prevent this?

 

I have tried to build into the Validation Rule an exception like this:

 

 

AND(

(OR (TEXT(PRIORVALUE(StageName)) = "Closed Won",

TEXT(PRIORVALUE(StageName)) = "Closed Won Renewal")),

NOT(OR(

ISCHANGED(ACV_GBP_New__c),

$Profile.Name = "System Administrator",

$Profile.Name = "Data Administrator"))

)

But the error message is still appearing and preventing the Opportunity from closing. 

 

Any help on this matter would be appreciated.

Serena

5 个回答
  1. 2018年11月14日 15:09

    Change VR to this:

    AND(

    ISCHANGED(StageName),

    OR(

    TEXT(PRIORVALUE(StageName)) = "Closed Won",

    TEXT(PRIORVALUE(StageName)) = "Closed Won Renewal"

    ),

    NOT(

    OR(

    $Profile.Name = "System Administrator",

    $Profile.Name = "Data Administrator"

    )

    )

    )

     

    @Sunil

     

    If we modify the rule your way, users might get around with changing the stage and ACV_GBP_New__c field simultaneously. So that's kind of loophole, don't you think?
0/9000