Overview
The “List Has No Rows For Assignment To SObject” error is one of the most common Salesforce errors and is caused when a query returns no data. This error prevents users from retrieving or displaying any data from the Salesforce database, preventing them from interacting with their Salesforce environment. This guide provides step-by-step instructions on how to fix this error and offers troubleshooting tips to help prevent it from occurring in the future.
Cause and Solution
The “List Has No Rows For Assignment To SObject” error usually occurs when a query returns no data. When this happens, Salesforce is unable to assign the query results to an SObject and throws an error instead. To fix this error, you need to identify the source of the query and resolve the issue that is preventing it from returning any data.
Step 1
Identify the source of the query:
- Is the query a SOQL or SOSL query?
- Is it a direct query, internal query, or third-party query?
- Is it coming from a Visualforce page, a custom controller, or the system logs?
Step 2
Resolve the issue preventing the query from returning any data:
- If it is a query issue, check the syntax of the query and debug it using the Developer Console.
- If it is an issue with Visualforce, check the syntax of the page and debug it using the Developer Console.
- If it is an issue with a custom controller, debug the controller code using the Developer Console.
Troubleshooting Tips
- Ensure that the SOQL or SOSL query is correctly formatted before executing it.
- Check for any invalid IDs or object names in the query before executing it.
- Double-check that any Visualforce pages have the correct syntax and are correctly linked to the custom controller before deploying them.
- If necessary, update your Salesforce version to the latest one.
FAQ
Q: How do I identify the source of the query?
A: You can identify the source of the query by checking if it is a SOQL or SOSL query, if it is a direct query, internal query, or third-party query, and if it is coming from a Visualforce page, a custom controller, or the system logs.
Q: How do I prevent this error from happening in the future?
A: You can prevent the “List Has No Rows For Assignment To SObject” error from occurring in the future by ensuring that the SOQL or SOSL query is correctly formatted before executing it, checking for any invalid IDs or object names in the query before executing it, double-checking that any Visualforce pages have the correct syntax and are correctly linked to the custom controller before deploying them, and updating your Salesforce version to the latest one if necessary.
**Source: **
https://developer.salesforce.com/forums/?id=906F00000008qhnIAA