Download page Object reference is not set to an instance of an object (Release 8).
Object reference is not set to an instance of an object (Release 8)
Cause
Related to a bad merge field or mismatching TableStart and TableEnd merge fields in adetail region.
What to Do
A good start is to remove paragraphs (or entire pages for larger templates) and repeat the merge until you find the issue. Then you can correct the merge field or detail region causing the problem.
For example, you may receive the error message if the TableStart and TableEnd merge fields are not in the same row of the detail region. The correct usage of TableStart and TableEnd merge fields is shown below.
Cause
You may also receive the error message if data with double quotes is being merged into an IF statement in a Microsoft Word template.
What to Do
Remove the double quotes from the field.
Create a new formula field orDV0parameter and reference the value of the existing field in a Salesforce SUBSTITUTE formula to remove all double quotes from the field value. Then reference the new formula field orDV0parameter within the IF statement.
Conga Conductor and Conga Workflow Release 8
Cause
For Conga Conductor and Conga Workflow, this error message is most commonly caused by field level security issues with the formula field that contains the Conga Conductor or Conga Workflow formula.
What to Do
Navigate to Salesforce Setup > Security Controls > Field Accessibility.
Select the object on which the field exists, selectView Fields, and then select the field.
Lastly, select the Profile of the user running the Conductor solution (or the Profile of theUser to Send asuser for Workflow) and ensure that Profile has visibility to the formula field.