> For the complete documentation index, see [llms.txt](https://docs.devolutions.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.devolutions.net/powershell-universal/da/portal/portal-widgets/dynamic.md).

# Dynamic

Brug komponenten Dynamic i PowerShell Universal til at generere PSBlazor-komponenter i farten ud fra PowerShell-script, herunder kontekstbevidste tabelkolonner.

Den dynamiske komponent giver Dem mulighed for at køre PowerShell-script for at generere PSBlazor-komponenter i farten. Komponenten er kontekstbevidst.

{% hint style="warning" %}
Fordi dynamiske komponenter kører PowerShell ved hver gengivelse, kan de reducere ydeevnen for Deres apps.
{% endhint %}

En dynamisk komponent defineres med en funktion, der udføres, når appen indlæses.

```xml
<Dynamic Function="RenderMyDynamic" />
```

I den dynamiske komponent skal De returnere en streng, der gengives. Den skal være gyldig PSBlazor-syntaks.

```powershell
function RenderMyDynamic {
    "<Alert Message='Cool!' />"
}
```

Hvis De bruger en dynamic i en komponent, der sætter en kontekstvariabel, kan De bruge konteksten i Deres funktion. I dette eksempel har vi en tabel over tjenester, der bruger en dynamic i statuskolonnen.

```markup
<Table DataSource="$Services">
    <PropertyColumn Property="Name" />
    <PropertyColumn Property="Status">
        <Dynamic Function="RenderStatusColumn" />
    </PropertyColumn>
</Table>
```

Funktionen `RenderStatusColumn` kaldes for hver række i tabellen.

```powershell
function RenderStatusColumn {
    param($Context)
    
    if ($Context.Status -eq 'Running')
    {
        "<Alert Message='Started' />"
    }
    else 
    {
        "<Alert Message='$($Context.Status)' />"
    }
}
```


---

# 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.devolutions.net/powershell-universal/da/portal/portal-widgets/dynamic.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.