> 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/aur0707.md).

# AUR0707

Template compilation error: creating binding to non-bindable property yyyy on zzzz.

### **Error message**

Template compilation error: creating binding to non-bindable property {{0}} on {{1}}.

### **Parameters**

1. `propertyName`: The name of the property that is not defined as bindable.
2. `attributeName`: The name of the custom attribute where the binding was attempted.

### Error explanation

This error occurs during template compilation when you try to bind a property within a multi-binding custom attribute, but that property is not declared as `@bindable` in the custom attribute's view model class.

Multi-binding syntax allows binding multiple properties of a custom attribute in a single attribute declaration, like this: `<div my-attribute="propA.bind: valueA; propB: valueB"></div>`

For this to work, both `propA` and `propB` must be declared as `@bindable` properties within the `MyAttributeCustomAttribute` class. If either `propA` or `propB` is missing the `@bindable` decorator (or is not defined at all), this error will be thrown for the non-bindable property.

### Common causes

* Forgetting to add the `@bindable` decorator to a property in the custom attribute's view model class that you are trying to bind using multi-binding syntax.
* A typo in the property name within the multi-binding attribute string (e.g., `proA.bind: ...` instead of `propA.bind: ...`).

### How to fix

* Ensure that every property you intend to bind within a multi-binding attribute string is decorated with `@bindable` in the corresponding custom attribute's view model.
* Double-check the spelling of property names in the multi-binding attribute string.

### Example of Incorrect Usage:

```typescript
// my-attribute.ts
import { bindable } from 'aurelia';

export class MyAttributeCustomAttribute {
  @bindable propA: string;
  // propB is missing @bindable
  propB: string;
}
```

```html
<!-- usage.html -->
<import from="./my-attribute"></import>

<!-- Error: propB is not bindable on MyAttributeCustomAttribute -->
<div my-attribute="propA.bind: valueA; propB: valueB"></div>
```

### Example of Correct Usage:

```typescript
// my-attribute.ts
import { bindable } from 'aurelia';

export class MyAttributeCustomAttribute {
  @bindable propA: string;
  @bindable propB: string; // Added @bindable
}
```

```html
<!-- usage.html -->
<import from="./my-attribute"></import>

<!-- Correct: Both propA and propB are bindable -->
<div my-attribute="propA.bind: valueA; propB: valueB"></div>
```


---

# 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/aur0707.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.