> 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/0901-to-0908/aur0903.md).

# AUR0903

Invalid Dialog Settings. You must provide either "component" or "template" or both.

### **Error message**

Invalid Dialog Settings. You must provide either "component" or "template" or both.

### **Parameters**

None

### Error explanation

This error occurs when you attempt to open a dialog using `IDialogService.open()` without providing either a `component` or a `template` in the settings object. At least one of these is required to define the content of the dialog.

### Common causes

* Calling `dialogService.open({})` with an empty settings object.
* Providing a settings object that omits both `component` and `template`.
* Dynamically creating the settings object and failing to include `component` or `template`.

### How to fix

* Ensure your dialog settings object includes at least one of the following properties:

  * `component`: A function returning a component constructor, instance, or promise thereof.
  * `template`: A string, HTML element, or a function returning a string, HTML element, or promise thereof.

  ```typescript
  // Example using component
  dialogService.open({ component: () => MyDialogComponent });

  // Example using template
  dialogService.open({ template: '<div>My Dialog Content</div>' });

  // Example using both
  dialogService.open({ component: () => MyDialogViewModel, template: myDialogTemplate });
  ```

### Debugging tips

* Check the settings object being passed to `dialogService.open()`.
* Verify that the `component` or `template` property is present and correctly defined.
* Use the browser debugger to inspect the settings object just before `dialogService.open()` is called.


---

# 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/0901-to-0908/aur0903.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.