Skip to main content
Conga Support

Using Detail Regions with If Statements

Using Detail Regions with If Statements can be tricky as there are some behaviors that could cause some errors. Most importantly you need to consider whether your report has the possibility of returning no data, if not set up properly your If Statement could be deleted. To avoid this issue you will have to isolate your TableStart/TableEnd to a line by itself.

If all your mergefields in an IF statement are coming from detail data, enclose the entire IF statement with TableStart and TableEnd fields, but leave them outside the IF statement. That way, if your report returns no data, our HOTFUR feature won't break the IF Statement.

 You must use traditional merge fields (not text based fields). The examples below are toggled open.

{MERGEFIELD TableStart:Case \* MERGEFORMAT }

{IF "<<CASE_STATUS>>"="Closed" "<<Close_Date>>" "Open" \ * MERGEFORMAT }

{MERGEFIELD TableEnd:Case \* MERGEFORMAT }

If only one of the Fields in an IF statement is being populated by detail data, you'll want to enclose ONLY that field in TableStart/TableEnd fields, and make sure this field has its own line.

{ IF "<<OPPORTUNITY_CLOSEDATE>>" = "<<TODAY>>"

<<TableStart:Case>> "<<Close_Date>>" <<TableEnd:Case>>

"Open" \ *MERGEFORMAT }

Maybe you have two different detail datasets you want to compare in one IF statement. The process for this is simply an extension of the above technique, where each dataset needs its own row.

{ IF "<<OPPORTUNITY_CLOSEDATE>>"="<<TODAY>>"

"<<TableStart:Case>> <<Close_Date>> <<TableEnd:Case>>"

"<<TableStart:Opportunities>> <<Close_Date>> <<TableEnd: Opportuntities>>"

" \* MERGEFORMAT }