> For the complete documentation index, see [llms.txt](https://docs.codegiganten.de/plugin-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.codegiganten.de/plugin-documentation/en/apps/search-intelligent-and-ai-optimized/feed-template-editor.md).

# Edit data fields

With the "Edit data fields" editor you decide, without programming skills, which product data goes to the search.

With the "Edit data fields" editor you decide which product data InsightSearch receives for the search. You do not need programming skills. All available fields are listed. You switch fields on or off and choose where the value comes from. You need the editor when a field is missing in the search, for example a property like "Color" or a custom field of your shop.

## How to open the editor

Click "Edit data fields" in **Sources** or in **Data attributes**. For push sources the page is called "Edit data fields (push index)". The button does not exist if the source is an external feed, because its fields cannot be changed here.

At the top right you find:

* **Save** (for push "Save field settings")
* **Test export** (pull only): Checks whether Shopware's product export can be generated without errors with these settings.

A blue info card summarizes the main points:

* "Active" means: the field is transferred and is then available in search, filters and search weighting.
* Changes take effect after the next "Re-import product data". After saving you can do this directly in the editor.
* Fields with a lock are fixed by InsightSearch. For your own assignments, check that source and value match, otherwise data will be missing in the search.
* With pull, the card shows whether a dynamic product group determines which products are transferred. "Open dynamic product group" takes you there. Without a group, all products of the sales channel are transferred.

## Search and filter

Above the list there is a search field ("Field name, property or source ...") and a counter such as "12 of 30 fields active". The selection buttons "All", "Active", "Inactive", "Required fields" and "Recommended" each show a count. While you search or filter, all groups are expanded. If nothing matches, it says "No fields match search and filter."

## The groups

The fields are in collapsible groups. Each shows how many of its fields are active.

| Group                   | Content                                                                                                        |
| ----------------------- | -------------------------------------------------------------------------------------------------------------- |
| Required fields         | Without these fields InsightSearch cannot show products in the search: id, price, title, link and image\_link. |
| Product data            | Standard fields from Shopware such as name, description, brand or dimensions.                                  |
| Properties              | Property groups such as color or size, good for filters and rules.                                             |
| Custom fields           | The custom fields of your own shop.                                                                            |
| Fields of other plugins | Custom fields created by other plugins. Usually of no use for the search. The group is collapsed.              |

Required fields carry the red label "Required". Recommended fields carry the blue label "Recommended": availability, brand, keywords and search\_keywords. Please use all required and recommended fields where possible; it improves the search and the product recommendations.

## The columns of a row

| Column | Meaning                                                                                                       |
| ------ | ------------------------------------------------------------------------------------------------------------- |
| Field  | The readable name, below it the technical name under which the field appears in filters and data attributes.  |
| Active | Whether the field is transferred. Newly transmitted fields are automatically active after the next re-import. |
| Source | Where the value comes from: "Product", "Property", "Custom field" or "Fixed value".                           |
| Value  | The specific field of the chosen source, for example the property group "Color".                              |

With the source "Product" readable values are offered, such as product number, EAN/GTIN, name, description, keywords, search terms, manufacturer, width, height, length, weight, sales unit or base unit. "Automatic (determined by the system)" is shown for fields that InsightSearch fills itself. The editor loads property groups and custom fields from your shop and shows "Loaded: {n} properties, {m} custom fields for products".

### Fixed fields with a lock

With pull, InsightSearch fixes some fields. They carry a lock, the switch cannot be changed, and the origin is shown as text, for example "Product → Name". With push there are no locks; all fields are editable.

### Your own fields

You can only rename a field if you created it yourself. With push you add a new field with "Add custom field". It appears as a new row with the source "Custom field" and is active.

### The "Badge" field

A badge is the small label on the product card, for example "Sale" in red. The field has its own rule editor. For each rule you set where the text comes from ("Text from", "Text field") and where the color comes from ("Color from", "Color / color field", or a color picker for "Fixed color"). "Add badge rule" creates another rule, "Remove" deletes one. At least one rule always remains.

## Save and re-import

1. Make your changes.
2. Click **Save**. "Data fields saved." appears.
3. A blue box says: "Saved. So that the search knows the new fields, re-import the product data once." Click **Re-import now**.

If you did not open the editor from Sources or Data attributes, you see a note to click "Re-import product data" under "Sources" in the plugin dashboard instead.

{% hint style="warning" %}
If your shop's export is generated by a scheduled task, as the plugin sets it up, changes only take effect with the next run of that task. Wait for it and re-import the product data afterwards. The editor points this out with its own note.
{% endhint %}

## Unsaved changes

If you leave the editor with unsaved changes, the "Unsaved changes" dialog asks: "You changed fields but did not save. Leave the page anyway?" With "Keep editing" you stay, with "Discard and leave" you leave without saving. Your browser also warns when you close or reload the browser tab. If you reverted a change, it does not count as unsaved.

<figure><img src="https://923488348-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FebcjSiStaIxyVJ83vjsL%2Fuploads%2Fgit-blob-c9723ca0d8455d92ec258fa85bdac782571ef1b1%2Fimage%20(95).png?alt=media" alt="Field editor of the product feed, view 1"><figcaption></figcaption></figure>

<figure><img src="https://923488348-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FebcjSiStaIxyVJ83vjsL%2Fuploads%2Fgit-blob-7501a6d6a7a9743b3d560eb1e9b671b17d2a78a9%2Fimage%20(96).png?alt=media" alt="Field editor of the product feed, view 2"><figcaption></figcaption></figure>

<figure><img src="https://923488348-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FebcjSiStaIxyVJ83vjsL%2Fuploads%2Fgit-blob-6a0a7f25250f41ca7558e182b1c97a5b9c54128c%2Fimage%20(97).png?alt=media" alt="Field editor of the product feed, view 3"><figcaption></figcaption></figure>

<figure><img src="https://923488348-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FebcjSiStaIxyVJ83vjsL%2Fuploads%2Fgit-blob-70f452feefcbd5353df6ae272f2f9c498388cd12%2Fimage%20(98).png?alt=media" alt="Field editor of the product feed, view 4"><figcaption></figcaption></figure>

## Further reading

{% content-ref url="/pages/UKhMX3Zla832boJXFREa" %}
[Sources](https://docs.codegiganten.de/plugin-documentation/en/apps/search-intelligent-and-ai-optimized/indices.md)
{% endcontent-ref %}

{% content-ref url="/pages/0hGQB6UOZSi6fc9UUDYL" %}
[Data attributes](https://docs.codegiganten.de/plugin-documentation/en/apps/search-intelligent-and-ai-optimized/data-attributes.md)
{% endcontent-ref %}

{% content-ref url="/pages/YEBvytB69E4Y4qAMmqvE" %}
[Filters](https://docs.codegiganten.de/plugin-documentation/en/apps/search-intelligent-and-ai-optimized/filters.md)
{% endcontent-ref %}


---

# 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://docs.codegiganten.de/plugin-documentation/en/apps/search-intelligent-and-ai-optimized/feed-template-editor.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.
