> For the complete documentation index, see [llms.txt](https://help.sdocs.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.sdocs.com/sdocs/advanced-template-logic/template-attributes/template-attributes-how-to-guides/how-to-handle-null-or-empty-values.md).

# How To: Handle Null or Empty Values

Use null-handling attributes when blank fields would confuse the reader.

### Problem

You need to display something meaningful when a field is null or empty.

### Solution 1: `nullprefix` and `nullpostfix`

**Display `N/A` for empty values:**

```
<column nullprefix="N/A">Optional_Field__c</column>
```

**Display `TBD` for empty dates:**

```
<p>Ship Date: {{!Opportunity.Ship_Date__c format-date="MM/dd/yyyy"}}</p>
```

If the field is null, this shows nothing.

**Better:**

```
<column nullprefix="TBD" format-date="MM/dd/yyyy">Ship_Date__c</column>
```

### Solution 2: Conditional Rendering

**Show different text for null:**

```
<!--{{!
<lineitemsSOQL>
<soql>SELECT Title FROM Contact WHERE AccountId = '{{!Account.Id}}'</soql>
<column render="RECORD.Title==null,No title provided,RECORD.Title"></column>
</lineitemsSOQL>
}}-->
```

### Solution 3: `allprefix` and `allpostfix`

**Add symbols regardless of null:**

```
<column allprefix="$" format-number="#,###.##">Optional_Amount__c</column>
```

**Result:** The `$` still appears even when the field is null.

### Tips

* Use `nullprefix` when you need placeholder text.
* Use `allprefix` when symbols should always appear.
* Combine with `render` for more complex null logic.
* Standard `prefix` and `postfix` do not render for null values.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.sdocs.com/sdocs/advanced-template-logic/template-attributes/template-attributes-how-to-guides/how-to-handle-null-or-empty-values.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.