> For the complete documentation index, see [llms.txt](https://docs.aurelia.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.aurelia.io/developer-guides/error-messages/0088-to-0723/aur0712.md).

# AUR0712

Template compilation error: Bindable property and attribute needs to be unique; found property: xxxx, attribute: yyyy

### **Error message**

Template compilation error: Bindable property and attribute needs to be unique; found property: {{0}}, attribute: {{1}}

### **Parameters**

1. `propertyName`: The name specified in the `property` attribute of the `<bindable>` tag.
2. `attributeName`: The name specified in the `attribute` attribute of the `<bindable>` tag (or `undefined` if not specified).

### Error explanation

This error occurs during template compilation when defining bindable properties for a local element using the `<bindable>` tag. It indicates that either the specified `property` name or the specified `attribute` name (if provided) has already been used by another `<bindable>` tag within the *same* local element definition (`<template as-custom-element="...">`). Both property names and attribute names must be unique for a single local element.

### Common causes

* Defining two `<bindable>` tags with the same `property` attribute value within the same `<template as-custom-element="...">`.
* Defining two `<bindable>` tags with the same `attribute` attribute value within the same `<template as-custom-element="...">`.

### How to fix

* Review the `<bindable>` tags within the specified local element definition.
* Ensure that each `property` attribute value is unique across all `<bindable>` tags for that local element.
* Ensure that each `attribute` attribute value (if specified) is unique across all `<bindable>` tags for that local element.
* Rename or remove the duplicate property or attribute definition.

### Example of Incorrect Usage:

```html
<!-- my-component.html -->
<template>
  <local-element message="Hi" data="Test"></local-element>

  <template as-custom-element="local-element">
    <!-- Error: Duplicate property name "message" -->
    <bindable property="message"></bindable>
    <bindable property="message"></bindable>

    <!-- Error: Duplicate attribute name "data-attr" -->
    <bindable property="data1" attribute="data-attr"></bindable>
    <bindable property="data2" attribute="data-attr"></bindable>

    <span>${message} ${data1} ${data2}</span>
  </template>
</template>
```

### Example of Correct Usage:

```html
<!-- my-component.html -->
<template>
  <local-element message="Hi" data-value="Test"></local-element>

  <template as-custom-element="local-element">
    <!-- Correct: Unique property and attribute names -->
    <bindable property="message"></bindable>
    <bindable property="dataValue" attribute="data-value"></bindable>

    <span>${message} ${dataValue}</span>
  </template>
</template>
```


---

# 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.aurelia.io/developer-guides/error-messages/0088-to-0723/aur0712.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.