What is a common reason a user cannot run a report?

What is a common reason a user cannot run a report?

• A. The report is too large
• B. They lack access to a required report field
• C. Their browser blocks the request
• D. The data source is invalid

Answer: (D)

A report can’t run if there isn’t a valid path to the data it should pull from. The data source defines where the report gets its information and how that information is retrieved. If the data source is invalid—maybe the object it points to was deleted, renamed, or you don’t have permission to access it—the system has nothing reliable to query, so the run fails with an error about the data source. Other issues like a report being very large can slow things down or timeout, and security restrictions on a field or a browser blocking a request are separate problems that don’t reflect a fundamental data source problem. The core blocker is the data source being invalid, because without a valid source, there’s no data to generate the report.

A report can’t run if there isn’t a valid path to the data it should pull from. The data source defines where the report gets its information and how that information is retrieved. If the data source is invalid—maybe the object it points to was deleted, renamed, or you don’t have permission to access it—the system has nothing reliable to query, so the run fails with an error about the data source. Other issues like a report being very large can slow things down or timeout, and security restrictions on a field or a browser blocking a request are separate problems that don’t reflect a fundamental data source problem. The core blocker is the data source being invalid, because without a valid source, there’s no data to generate the report.