> 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/fr/portal/portal-widgets/dynamic.md).

# Dynamique

Utilisez le composant Dynamic dans PowerShell Universal pour générer des composants PSBlazor à la volée à partir d'un script PowerShell, y compris des colonnes de tableau contextuelles.

Le composant dynamic vous permet d'exécuter un script PowerShell pour générer des composants PSBlazor à la volée. Il est contextuel.

{% hint style="warning" %}
Comme les composants dynamiques exécutent PowerShell à chaque rendu, ils peuvent réduire la performance de vos applis.
{% endhint %}

Un composant dynamique est défini avec une fonction qui sera exécutée au chargement de l'appli.

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

Dans le dynamic, retournez une chaîne qui sera rendue. Elle doit respecter une syntaxe PSBlazor valide.

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

Si vous utilisez un dynamic dans un composant qui définit une variable de contexte, vous pouvez utiliser le contexte dans votre fonction. Dans cet exemple, nous avons un tableau de services qui utilise un dynamic dans la colonne d'état.

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

La fonction `RenderStatusColumn` sera appelée pour chaque ligne du tableau.

```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/fr/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.