Skip to main content
Hi,

 

We are EE users, who have been having som trouble recently with a calculated date field that I created on a custom object.

 

We use the following formula to calculate and Expiry Date by adding a number of months to a start date that users can set or upload, in British format:

 

DATE(YEAR(Cover_Start_Date__c)+ FLOOR(MONTH(Cover_Start_Date__c) + Months_Cover__c -1) /12 ,

 

MOD(MONTH(Cover_Start_Date__c )+ Months_Cover__c -1,12) +1,

 

DAY( Cover_Start_Date__c ))-1

 

This formula worked perfectly from when it was created (Dec 11) until recently (apr. early June, and used it sucessfully for a couple of massive report jobs in April/May, so know it was working well until then).

 

The problem we are having is that although the date is still apearing correctly on the Object, we cannot use the field in either object summaries/overviews or in the Reports function. If I attempt to move the field over into the report, I get this error message:

 

One of the date fields in your report was invalid. Check your records and formulas for errors. They may contain or produce non-existent dates, like February 30, or ones that are out of bounds. Edit this report and click Remove All Columns to start over.

 

I've checked, and the formula is producing Feb 28/29th correctly, and I also checked that the reports have no filters that exclude particular dates (though the normal report situation would be to come up with blank results rather than an error in that case anyway).

 

One other thing I noticed was that this error coincided with two other issues with Salesforce - firstly, that unless we were careful with formats, the system would 'jumble' dates into the American format, which we'd never had to do before. Secondly we had an issue where several of our formulae, those which 'hang' off the one we're having trouble with, froze for two days with all showing as 'calculating'. This issue resolved itself before we spoke to Salesforce, but that is where we first found this date error, so I've added it in as extra contextual imformation.

 

Does anyone have any ideas as to why we can no longer use this field in Reports? I can't easily find where the error lies in the formula if there is one, as I can't see a report of all the different results it produces!

 

Any help would be much appreciated.
답변 3개
  1. 2012년 7월 24일 오후 1:27
    Would the time this formula stopped working been around the time your organization received the Summer 12 update?

     

    --KC
0/9000