The features you’ll actually use: Impersonation, Show All Fields, Logical Names, Option Values
What it is
Level Up is a browser extension that adds a toolbox to Dynamics 365 / model-driven apps so you can do common “power user” actions (IDs, logical names, option values, field visibility, refresh tools, impersonation) without bookmarklets.
You’re here because…
- UAT is blocked by: “It works for me (admin) but not for them (user).”
- You need to see field values that aren’t on the form (and your flow/script uses them anyway).
- You keep needing logical names and choice numeric values for Power Automate conditions and JS.
- You want “receipts” fast (record ID, URL, values, what changed).
Chrome vs Edge (for Level Up)
Day-to-day: basically the same. Both are Chromium and Level Up is available for both stores.
Why you might choose Edge
- Easier to standardize in many Microsoft-heavy orgs (admins often manage Edge extensions more actively).
Why you might choose Chrome
- If your team already uses Chrome everywhere, it’s the path of least resistance.
Practical move: use whichever browser your org supports best — the value is the extension, not the browser.
Fast path setup (5 minutes)
- Install Level Up in your browser.
- Open a record form in your model-driven app.
- Use the sidebar/full mode if available — that’s where the “serious” tools live (including impersonation).
The features that matter (ranked by real usefulness)
1) Impersonation (aka “UAT security testing without losing your mind”)
What it is
A way to temporarily test the app as another user so you can confirm whether an issue is security/role-related vs “the system is broken.”
Why it’s a big deal
Most security debugging fails because people test as admin. Impersonation lets you answer, quickly:
- “Can this specific role see the record?”
- “Can they edit it?”
- “Can they set this lookup / run this command?”
Proceed with caution
- Treat impersonation as admin-only behavior and use it with intent.
- Team rule: if you use it, document who you tested as and what you observed (so it’s auditable and repeatable).
Use case: UAT tester says “I can’t submit.” You impersonate them, reproduce in 30 seconds, and now you know whether it’s a missing privilege, field security, or a form rule.
2) Show All Fields (the debugging cheat code)
What it is
A panel that shows all fields and values (often including internal names), not just what’s placed on the form.
Why it’s insanely useful for Power Automate + debugging
Flows and scripts don’t care whether the field is on the form — they care whether it’s populated. This tool helps you answer:
- “Is the field actually blank, or just not visible on the form?”
- “Did my flow update the value, but the form doesn’t show it?”
- “Am I using the wrong field entirely?” (happens more than anyone admits)
Use case: Your flow checks a field like new_topic but users swear it’s empty. Show All Fields reveals it’s populated… they’re just looking at the wrong form or a different field.
3) Option/Choice Values (stop comparing labels in flows)
What it is
Shows the numeric values behind choice fields (option sets).
Why it matters
Power Automate conditions usually need the value, not the label. This tool turns “guessing” into “copy/paste.”
Use case: “Approved” fails in a condition → you pull the numeric code and the flow starts behaving.
4) Logical Names (schema names on demand)
What it is
Displays logical/schema names for fields/tabs/subgrids so you can build JS, queries, and mappings correctly.
Use case: You’re writing JS or debugging a flow expression and need the real column name now.
5) Record ID + Record URL (instant receipts)
What it is
Quickly grabs the record GUID and URL so you can paste it into:
- bug reports
- Teams messages
- flow run notes
- UAT scripts
6) Small quality-of-life tools that add up
These are “not glamorous” but you’ll use them a lot:
- Refresh all subgrids / refresh form quickly
- Highlight changed fields (great before save)
- Blur fields (for screenshots without leaking real data)
“Do this when…” (simple use cases)
“UAT says it’s a security issue”
- Use Impersonation
- Reproduce as the user
- Now you can say: record access vs field security vs privilege (Append/Append To, Create, Write)
“My flow uses a field that’s not on the form”
- Use Show All Fields
- Confirm whether the field is populated
- Confirm you’re using the right field
“My choice condition won’t match”
- Use Option/Choice Values
- Use the numeric value in your condition
“I need the schema name for JS or mappings”
- Use Logical Names
- Copy the internal name, move on with your life
Gotchas + safe-use rules
- Don’t use “power” features to do production edits “faster.” Tools are for troubleshooting; fixes should be done through the right process.
- Impersonation: treat like admin tooling — use intentionally, document what you tested.
- Extensions are still software: if this is for a client/org rollout, get it approved like any other tool.
Definition of Done
You’re “Level Up effective” when you can produce, in under 2 minutes:
- ☐ Record ID + URL for any issue
- ☐ Confirm actual field values (even if not on the form)
- ☐ Get choice numeric codes for flow logic
- ☐ Verify security/UAT behavior by impersonating the tester
Printable cheat sheet
Top 5 clicks
- Impersonation (UAT/security testing)
- Show All Fields (debug flows + hidden values)
- Option/Choice Values (numeric codes)
- Logical Names (schema names)
- Record ID / Record URL (receipts)
Team safety defaults
- Impersonation = admin-only, document tests
- Use tools to diagnose, not to bypass governance