> For the complete documentation index, see [llms.txt](https://help.craftsmanplus.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.craftsmanplus.com/play/catalogue/connecting-your-project/mapping-layers-to-catalogue-columns.md).

# Mapping Layers to Catalogue Columns

After a catalogue is linked to a project and its active conditions are selected, the next step is to connect individual layers in your playable to the catalogue’s content columns.

This process is called *mapping*, it defines which catalogue values control which layers at runtime.

Each content column in the catalogue (text, image, or URL) can be mapped to a layer in the project.\
When the playable runs, those layers will automatically display the content from the active catalogue row that matches the user’s conditions (like Language, Device, or Time).

### **How to Map a Layer:** <a href="#how-to-map-a-layer" id="how-to-map-a-layer"></a>

{% stepper %}
{% step %}

### Within your CRAFTSMAN PLAY project, select the layer you want to connect.

{% endstep %}

{% step %}

### At the top of the Layer Properties panel, enable the Dynamic Content section, then click to open it.

This is the same way you would enable it for the other Dynamic Content system.
{% endstep %}

{% step %}

### Click the “+” icon, and choose the new “Catalogue” option.

{% hint style="warning" %}
DO NOT choose Time, Device, Language, etc., that is for the other Dynamic Content System
{% endhint %}
{% endstep %}

{% step %}

### Click the dropdown to see all available content columns from the linked catalogue.

{% endstep %}

{% step %}

### Choose the column you want to map to the respective layer property.

{% endstep %}

{% step %}

### If more layer properties can be mapped, more dropdowns will appear.

For instance, you can map the button image column to the layer image, and the button URL column to the Launch URL.
{% endstep %}

{% step %}

### Connected layers will display an icon in the layers panel

Dynamic Content and 3rd Party Call icons will appear next to each connect layer in the layers panel.

<figure><img src="https://3019081569-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZBycFFNxrdS0X9OsGtmT%2Fuploads%2Fgit-blob-a597699cceeae4436ce4d916521abbf206ba657d%2Fimage-20251112-202844.png?alt=media" alt=""><figcaption></figcaption></figure>
{% endstep %}
{% endstepper %}

<br>


---

# 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://help.craftsmanplus.com/play/catalogue/connecting-your-project/mapping-layers-to-catalogue-columns.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.
