Ask Search:
Liz DwanLiz Dwan 

Error: This report can no longer be edited or run. Your administrator has disabled all reports for the custom object, or its relationships have changed.

Custom Object has Enable Reports ticked but when I try to drag a report into the dashboard I received this error. Please can you explain if there is somewhere I need to enable dashboards or something else?
Best Answer chosen by Miglena (Salesforce.com) 
Mayank SrivastavaMayank Srivastava
Liz , it might have been one of the following that is causing it:
1. An object used in the relationship is not enabled for reporting
2. A look-up relationship used in the report was deleted or changed its type (changing from master-detail to look-up also makes a report obsolete)
3. An object in the report was deleted.
4. A profile does not have visibility to an object
5. The report is based on an object that belongs to a “managed package”  “In Development” status, therefore not all users will have access to it.

Reference:
http://simplysfdc.blogspot.com/2014/06/salesforce-obsolete-report.html

Check if it's any of the above.

If not, then the following:
The dashboard component was based on a new custom object, which will be the target for snapshots.  Nothing special there.  No lookup or master-detail fields on it.  The object had been deployed, and I can view the underlying report just fine.  Well, there's one thing I'd forgotten, it turned out:  the dashboard is a dynamic one.  And the new object has not been opened up to any profile.  That means no one can really see that dashboard component other than folks who can "view all".  That's not good in production of course... but I'm not quite there yet.  The thing has to be reviewed by admins first before opened up to anyone.

Looks like I need to at least allow access to the object by at least one profile explicitly before I can do anything about it in dashboards.
http://digicomet.blogspot.com/2011/04/this-report-can-no-longer-be-edited-or.html


As a last resort, try rebuilding the report. (crate it froms cratch)

All Answers

Mayank SrivastavaMayank Srivastava
Liz , it might have been one of the following that is causing it:
1. An object used in the relationship is not enabled for reporting
2. A look-up relationship used in the report was deleted or changed its type (changing from master-detail to look-up also makes a report obsolete)
3. An object in the report was deleted.
4. A profile does not have visibility to an object
5. The report is based on an object that belongs to a “managed package”  “In Development” status, therefore not all users will have access to it.

Reference:
http://simplysfdc.blogspot.com/2014/06/salesforce-obsolete-report.html

Check if it's any of the above.

If not, then the following:
The dashboard component was based on a new custom object, which will be the target for snapshots.  Nothing special there.  No lookup or master-detail fields on it.  The object had been deployed, and I can view the underlying report just fine.  Well, there's one thing I'd forgotten, it turned out:  the dashboard is a dynamic one.  And the new object has not been opened up to any profile.  That means no one can really see that dashboard component other than folks who can "view all".  That's not good in production of course... but I'm not quite there yet.  The thing has to be reviewed by admins first before opened up to anyone.

Looks like I need to at least allow access to the object by at least one profile explicitly before I can do anything about it in dashboards.
http://digicomet.blogspot.com/2011/04/this-report-can-no-longer-be-edited-or.html


As a last resort, try rebuilding the report. (crate it froms cratch)
This was selected as the best answer
Sunil ShahSunil Shah
Thanks Mayank :)
Azlan AbdullahAzlan Abdullah
@Mayank Srivastava thank you, appreciate it!
Jim MitchellJim Mitchell
To add to this... If one user can run the report and another can't, look at permission sets to be sure they don't differ between the users. A user with a permission set that can read an object will be able to run reports, while a user with permission set that cannot read the object will get the "This report can no longer be edited or run." error. This is, of course, presuming the Profile already does not have read access.
Jeff SchaumburgJeff Schaumburg
If it is 4. A profile does not have visibility to an object, does that mean that the user will never have access to the reports?