---
title: AsEnumerable Support
slug: blueprint/asenumerable-support
docTags: yO7XZ9PJxDCKZ-Mf4TSYB
createdAt: 2026-04-17T18:28:53.187Z
---

:::CtaButton{label="🟢 Migrator" openInNewTab="false"}

:::

AsEnumerable is a DataTable extension method that UiPath includes automatically, making it invisible to developers. In Power Automate Desktop, the underlying assembly must be explicitly referenced — otherwise migrated flows that use this extension will fail.

The required assembly is **System.Data.DataSetExtensions.dll**, which is part of the standard .NET framework.

# Recommended Setup: Install the .NET Developer Pack

The simplest and most complete solution is to install the .NET developer pack directly from Microsoft. This resolves the AsEnumerable issue and any other missing assembly references that may surface in migrated flows.

::::WorkflowBlock
:::WorkflowBlockItem
Download the .NET 4.7.2 Developer Pack from Microsoft.
:::

:::WorkflowBlockItem
Run the installer — assemblies are installed to C:\Program Files (x86)\Reference Assemblies.
:::

:::WorkflowBlockItem
In that folder, **delete or move** the **System.EnterpriseServices** files — PAD cannot load these and they will cause errors.
:::

:::WorkflowBlockItem
In **Init\_Variables**, set %defaultRunDotNetScriptReferences% to:
C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\\.NETFramework\v4.7.2
:::

:::WorkflowBlockItem
In **Init\_Variables**, set %defaultRunDotNetScriptImports% to:
System.Data.DataSetExtensions
:::
::::

## Alternative: Custom Modules Folder

If installing the developer pack isn't possible, you can manually locate and reference the assembly.

::::WorkflowBlock
:::WorkflowBlockItem
Create a **custom-modules** folder — Blueprint recommends placing it in the PAD installation folder.
:::

:::WorkflowBlockItem
Search your filesystem for **System.Data.DataSetExtensions.dll**.
:::

:::WorkflowBlockItem
Copy the file into your custom-modules folder.
:::

:::WorkflowBlockItem
In **Init\_Variables**, set %defaultRunDotNetScriptReferences% to the path of your custom-modules folder.
:::

:::WorkflowBlockItem
In **Init\_Variables**, set %defaultRunDotNetScriptImports% to:
System.Data.DataSetExtensions
:::
::::

:::hint{type="warning"}
The developer pack approach is strongly recommended — it's more robust and covers additional missing references you may encounter as you migrate more processes.
:::