# INVALID_SCREEN_DATA in WhatsApp Flows: Property 'example' is allowed only as a top level property of data model. Here's the Fix
Author: Prashant Jangid
Author URL: https://www.heltar.com/blogs/author/prashant-jangid
Published: 2025-05-16
Category: Troubleshoot
Category URL: https://www.heltar.com/blogs/category/troubleshoot
Tags: WhatsApp Flows Error
Tag URLs: WhatsApp Flows Error (https://www.heltar.com/blogs/tag/whatsapp-flows-error)
URL: https://www.heltar.com/blogs/invalidscreendata-in-whatsapp-flows-property-example-is-allowed-only-as-a-top-level-property-of-data-model-heres-the-fix-cmaqo9tw7008dkwl4audg3qd3

Seeing this error?

**INVALID\_SCREEN\_DATA**

**Property 'example' is allowed only as a top level property of data model. Invalid entry: '(path to error)'.**

That means you've placed the \_\_example\_\_ field inside a nested schema, which is not allowed in WhatsApp Flows.

## The Fix (TL;DR):

Move the \_\_example\_\_ property to the top level of your data model — not inside properties or nested objects.

### Correct:

```
"data": {
  "initial_values": {
    "type": "object",
    "properties": {
      "number": {
        "type": "number"
      }
    }
  },
  "__example__": {
    "initial_values": {
      "number": 8553906697
    }
  }
}
```

### Incorrect:

"properties": {

"number": { "type": "number" },

"\_\_example\_\_": { "number": 8553906697 }

}

## Why This Happens

WhatsApp Flows uses \_\_example\_\_ for previewing and testing data, but it only supports it at the root level of the data object. Nesting it inside properties or any sub-object results in an invalid schema.

In your original schema:

```
"initial_values": {
  "type": "object",
  "properties": {
    "number": { "type": "number" },
    "__example__": { "number": 8553906697 } // Invalid
  }
}
```

This usage breaks the schema validation.

### Best Practices

- Always define \_\_example\_\_ alongside your top-level data fields, not inside nested objects.

- Structure it to match the shape of your data model for clear previews and debugging.

- Keep your schema clean by separating structure (type, properties) from sample data (\_\_example\_\_).


This error is all about placement. Once you know that \_\_example\_\_ belongs only at the top, it’s a quick fix. Keep your data model clean, and your Flow will stay error-free. For more troubleshooting insights related to WhatsApp Business API, check out [heltar.com/blogs](https://www.heltar.com/blogs).


---
This blog is powered by Superblog. Visit https://superblog.ai to know more.
---