> For the complete documentation index, see [llms.txt](https://helpcenter.channable.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://helpcenter.channable.com/list-advertise/list-and-advertise-nl/op-kanalen-plaatsen/problemen-met-feeds-oplossen/het-probleem-met-het-lege-veld-oplossen.md).

# Het probleem met het 'lege veld' oplossen

### **Probleem**

**'** **'description'/'size'/'brand' is leeg**

## **Wat betekent dit probleem?**

Dit probleem betekent dat het veld dat je hebt gekoppeld in de **Mapping** stap voor 'description', 'size' of 'brand' leeg is voor een aantal items.

<figure><img src="https://content.gitbook.com/content/F8GepmoSonQRG6RnHOxJ/blobs/ypUs5ukhQpsGyqMYiYDs/360007448159" alt=""><figcaption></figcaption></figure>

### **Hoe los ik dit probleem op?**

* **De gegevens staan in een ander veld:** Als bijvoorbeeld de 'size' leeg is voor sommige producten maar je hebt de maat in je titels, kun je een [zoek naar waarde-regel](/manage-improve-product-data/manage-product-and-improve-data-nl/regels-bulkbewerken-en-verrijken/acties-dan-gebruiken-in-regels/regelactie-zoek-naar-waarde.md) gebruiken om de ontbrekende maten in te vullen.
* **De gegevens staan niet in een ander veld:** Voeg de informatie toe via je importbestand.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://helpcenter.channable.com/list-advertise/list-and-advertise-nl/op-kanalen-plaatsen/problemen-met-feeds-oplossen/het-probleem-met-het-lege-veld-oplossen.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
