#  INVALID_SCREEN_DYNAMIC_DATA in WhatsApp Flows: Data model schema is invalid for '${expression}'. Missing schema for ${objectProperty}? 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/invalidscreendynamicdata-in-whatsapp-flows-data-model-schema-is-invalid-for-dollarexpression-missing-schema-for-dollarobjectproperty-heres-the-fix-cmaqo35jb008ckwl4xu13w93o

Seeing this error?

**INVALID\_SCREEN\_DYNAMIC\_DATA**

**Data model schema is invalid for '${expression}'. Missing schema for ${objectProperty}.**

This means your dynamic data is missing required properties for a component — typically labels or values expected in list-type components like CheckboxGroup.

### The Fix (TL;DR):

When using a component like CheckboxGroup, the objects in your data array must include both label and value fields.

Add this to your schema:

```
"products": {
  "type": "array",
  "items": {
    "type": "object",
    "properties": {
      "id": { "type": "string" },
      "label": { "type": "string" },
      "value": { "type": "string" }
    },
    "required": ["label", "value"]
  }
}
```

### Why This Happens

You're binding CheckboxGroup to data.products, but each product object only contains id:

```
"properties": {
  "id": { "type": "string" }
}
```

But CheckboxGroup requires label and value properties to render correctly.

### Corrected Example

```
"products": {
  "type": "array",
  "items": {
    "type": "object",
    "properties": {
      "id": { "type": "string" },
      "label": { "type": "string" },
      "value": { "type": "string" }
    },
    "required": ["label", "value"]
  },
  "__example__": [
    {
      "id": "001",
      "label": "Product A",
      "value": "product_a"
    }
  ]
}
```

This satisfies the CheckboxGroup schema and avoids runtime errors.

### Best Practices

- Always check what properties your component expects. For lists, it’s often label and value.

- Use the required array in your schema to enforce data integrity.

- Include good \_\_example\_\_ data to preview and test early.


This validation error is about missing structure — not bad logic. WhatsApp Flows needs a precise data model that aligns with the UI components you use. Once you define the right fields, your Flow will render without issues. 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.
---