🕵️♂️ Uncover the Hidden Tables: Master “List Rows from Selected Environment” in Power Automate

💡 “Some techniques aren’t hidden by complexity — they’re hidden because most never thought to look.”

We all know the List rows from selected environment action. It’s a cool feature that lets you dynamically query Dataverse tables from any environment—Dev, QA, Prod—at runtime.

🔎 What Makes This Action Special?

This action gives your flow cross-environment capabilities — allowing you to query a different Dataverse environment at runtime using its environment URL.

But the best-kept secret?

Some tables — especially many-to-many relationships, custom intersect tables, and certain system tables — do not appear in the Table name dropdown. But you can still use them.

You just need to know how.

🛠️ Input Parameters

Environment

This input expects the Dataverse Web API URL, not the environment GUID.

🧭 Where to find it:

1. Go to https://make.powerapps.com

2. Select your environment

3. Click the ⚙️ Settings icon → Developer Resources

4. Copy the Web API value (e.g., )

💡 Tip: Store these URLs in a config table to dynamically switch environments without hardcoding.

Table Name

This expects the EntitySetName — the plural logical name of the Dataverse table.

❗The dropdown will not show many-to-many or intersect tables like , , etc.

💡 Tip: To find all valid EntitySetNames (even hidden ones), use this:

Paste the manually into the "Enter custom value" input.

Select Columns

Comma-separated logical column names like:

💡 Tip: Use to reduce payload size and avoid crossing the 4MB limit.

Filter Rows

OData filter expression — e.g.:

Sort By

OData-style sorting — e.g.:

💡Tip: Always sort by a deterministic column to avoid pagination issues.

Expand Query

This retrieves related data like lookup fields.

💡 Tip: Writing manually is tough. Use Power Apps Monitor:

1. Run a form or gallery load with lookups.

2. Open Monitor, inspect the network call.

3. Copy the auto-generated expression.

Example:

FetchXML Query

FetchXML is an XML-based query language with rich capabilities.

💡Tip: Use XrmToolBox's FetchXML Builder to visually build queries. If FetchXML is used, it overrides , , , and .

Row Count

Maximum number of rows to return.

💡Tip: Set higher than 2000 and enable pagination in flow settings.

Skip Token

Used for manual paging. Automatically handled in most cases.

Return Full Metadata

Enables full OData metadata in the response. Rarely used in flows unless for debugging or advanced parsing.

🧩 Real Mission: Query Hidden Many-to-Many Table

🎯 Goal: Get users linked to a team using

Steps:

• Environment: Use as your Dataverse Web API URL.

• Table Name: (manually enter this as it's hidden from the dropdown).

• Select Columns: Choose only what you need. In this case:

• Filter Rows: Apply a targeted filter like: teamid eq '679401ff-561d-ee11-9cbe-002248249aa1'

• Sort By: Sort by to ensure consistent pagination.

• Row Count: Set to to retrieve more than the default.

✅ Result: You’ve successfully queried a hidden many-to-many intersect table across environments using all supported parameters — efficiently and precisely, without writing custom code.

✅ Why Use This Action

• 🌍 Multi-Environment Magic

• 🧱 Access ALL Tables (including hidden/intersect)

• 🧠 Advanced Filtering via OData or FetchXML

• ⚡ Optimized Responses with ,

• 🔄 Reusable Logic for multiple environments

⚠️ What to Watch Out For

• 🔒 Case-sensitive table and column names

• 🚧 FetchXML overrides other filters silently

• 🔐 Proper permissions required in target environment

• ❗ Manual discovery needed — invalid table = silent failure

• 🧪 Still in preview — validate thoroughly before production

🧙‍♂️ Sensei-Level Flow Hacks

• Metadata Cache Table Create a config table that stores friendly names, , and environment URLs.

• Monitor = Your Best Friend Use Power Apps Monitor to discover how Power Apps builds and filters.

• Parallel Queries Add parallel branches for each environment → gather → merge → report.

🧭 Final Thoughts

“List rows from selected environment” isn’t just another action — it’s your passport to cross-environment automation and unlocked Dataverse potential.

When you master hidden table access, OData tricks, and metadata tools — you go from automating to commanding environments.

📣 Let’s Talk Summons

Have you tapped into hidden intersect tables? Pulled off an environment-hopping query? Or stumbled on quirks worth sharing? Let’s talk below and sharpen each other’s techniques. 💬

🚀 Follow for more deep dives in the #JulyAutomationSeries

Hey there, I’m Ajay! 👋 I'm all about Tech and creating fun, intuitive solutions. I blend technical skills with creativity to make the impossible possible! If you want to follow my nerdy adventures, you’re in the right place—stick around for more insights and tech tips to fuel your development journey! 🚀