Skip to main content
I am doing a review of a prospects database and what I am finding is that the CloseDate of an Opportunity is populated, yet the IsClosed (presumably a system level binary field is not exposed, I only see the Closed field under the Opportinty reporting option) and this field is not being populated...  The issue that I am seeing is that the Age of an Opportunity continues to increase based on the fact that IsClosed is not set in spite of the Closed Date being populated, so I believe that a validation Rule should be in place to Force IsClosed when the CloseDate is populated...  Can an expert please validate my belief...  ;>)

 

The second issue that I am seeing is that the ClosedDate can be set to a date BEFORE the CreateDate of an Opportunity, again, I believe that a Validation Rule should be in place to prevent the population of a ClosedDate to any value LT the CreatedDate...  And presumably the CreateDate = CloseDate is only for erroroneous set ups...

 

Once again can an expert please validate my belief...  ;>)
6 respostas
  1. 9 de out. de 2017, 18:37
    I would use the isClosed field -- not the picklist values, because if a value is changed, or a new one is added, your VRule would not work.

     

     

    AND(

    isClosed,

    CloseDate < DATEVALUE(CreatedDate)

    )

     

     
0/9000