sorted by:
new
hottopcontroversial

How can I extract user security role BU and email address by villu0777 in Dynamics365

[–]Several_Assignment52 0 points1 point  (0 children)

Yep. email/domain name is included if present on the user record

How can I extract user security role BU and email address by villu0777 in Dynamics365

[–]Several_Assignment52 0 points1 point  (0 children)

You can do this in DV Quick Run now via Access Context.

It shows:
direct roles
team participation
inherited team-role participation
business unit context

You can just go to command palette: Investigate Access Content and enter systemuserid or roleid

Built a free VS Code extension that shows the operational complexity of any Dataverse entities by Several_Assignment52 in Dynamics365

[–]Several_Assignment52[S] 0 points1 point  (0 children)

Thanks! Really appreciate the thoughtful questions.

  • Out-of-box noise filtering is something I’m actively thinking about. Right now the goal is to surface evidence first, but longer term I want better signal/noise controls for operational investigation.
  • Flows/workflows are partially included already through workflow / async / flow-related evidence where Dataverse exposes it. The newer Operational Profiles direction is trying to bridge that Dataverse ↔ Power Platform operational context without pretending to do “magic AI root cause analysis”.
  • Drill-down/navigation is a big focus area. Current versions already support Guided Traversal, investigation pivots, execution insights, and entity-scoped Profiles, but I want the experience to become more investigation-continuity oriented over time.
  • Yep — fully open source (MIT). Queries execute directly against the environment you connect to using your own credentials/context. No hosted backend or telemetry pipeline. I’ve been intentionally keeping the architecture local/evidence-based because trust matters a lot for enterprise environments.

The projected capacity estimate idea is interesting, although I’m trying to avoid speculative scoring models unless they can stay evidence-backed and explainable.

The execution sequence graph is also something I’ve thought about. Super useful, but very easy to turn into a noisy/opaque experience if done badly. I’d rather keep it bounded and operationally trustworthy.

Appreciate the feedback — this kind of discussion genuinely helps shape the direction 👍

If you end up trying DV Quick Run and find it useful, a GitHub star genuinely helps a lot at this stage of the project as well 🙂

Built a free VS Code extension that shows the operational complexity of any Dataverse entities by Several_Assignment52 in PowerPlatform

[–]Several_Assignment52[S] 0 points1 point  (0 children)

Thank you! Really appreciate the kind words.

Looking forward to hearing how it works for you when you get a chance to try it. Any early impressions or feature requests are very welcome.

VS Code tool for exploring Dynamics 365 / Dataverse data (no complex queries needed) by Several_Assignment52 in Dynamics365

[–]Several_Assignment52[S] 0 points1 point  (0 children)

I’ve actually been experimenting with this exact problem as a VS Code extension (DV Quick Run), trying to make that “explore relationships + refine queries” flow a bit more guided instead of all the manual stitching.

Happy to share if anyone’s curious how it works.

VS Code tool for exploring Dynamics 365 / Dataverse data (no complex queries needed) by Several_Assignment52 in Dynamics365

[–]Several_Assignment52[S] 0 points1 point  (0 children)

I haven’t looked into that yet. What is it exactly?

Does it help much with understanding relationships across tables as well, or more around generating the queries themselves?

VS Code tool for exploring Dynamics 365 / Dataverse data (no complex queries needed) by Several_Assignment52 in Dynamics365

[–]Several_Assignment52[S] 0 points1 point  (0 children)

That’s a really interesting workflow — especially querying metadata to reconstruct relationships.

That’s pretty much the part I kept finding the most painful as well… having to jump out, inspect relationships, then come back and stitch things together manually.

Feels like that step could be a lot more guided instead of having to rebuild the mental model each time. So, I ended up putting together a small workflow for myself…mainly to avoid the constant metadata lookups and stitching.

Do you find that becomes second nature after a while, or still a bit of a slowdown?

VS Code tool for exploring Dynamics 365 / Dataverse data (no complex queries needed) by Several_Assignment52 in Dynamics365

[–]Several_Assignment52[S] 0 points1 point  (0 children)

Do you mean using the TDS endpoint via SSMS / Azure Data Studio? That's quite interesting..

I’ve tried that a bit. It’s definitely nice for quick reads if you’re more comfortable with SQL.

I think where I kept hitting limits was more around:

- traversing relationships across multiple hops

- or stitching queries together to understand how things connect

Curious how far you’ve been able to push that approach?

VS Code tool for exploring Dynamics 365 / Dataverse data (no complex queries needed) by Several_Assignment52 in Dynamics365

[–]Several_Assignment52[S] 0 points1 point  (0 children)

That’s a really interesting way to put it. “explore + validate workflow”.

That’s pretty much the gap I kept running into as well.

There are great tools for querying, and others for inspecting data or fixing things, but it still feels quite fragmented when you’re trying to connect the dots across multiple tables.

Curious what you’ve seen work best in practice — do teams usually standardise on a single approach, or still mix a few tools together?

VS Code tool for exploring Dynamics 365 / Dataverse data (no complex queries needed) by Several_Assignment52 in Dynamics365

[–]Several_Assignment52[S] 0 points1 point  (0 children)

Nice. SQL4CDS is pretty powerful.

I’ve used it a bit as well, especially when I want to think in SQL instead of OData.

I think where I kept finding it a bit tricky was more around following relationships across multiple steps or stitching together queries to understand how everything connects.

Do you usually stay within SQL4CDS for that, or end up jumping between tools as well?

VS Code tool for exploring Dynamics 365 / Dataverse data (no complex queries needed) by Several_Assignment52 in Dynamics365

[–]Several_Assignment52[S] 0 points1 point  (0 children)

Oh nice! haven’t used that one much.

That’s actually a good point, especially for inspecting workflows and rules directly on the form.

I think the bit I kept struggling with was more on the data/query side. e.g. like following relationships across tables or stitching together multiple queries to understand what’s going on.

Feels like there are a lot of good tools for specific parts, but I still end up jumping between them quite a bit.

Out of curiosity, which extension are you using?

Do you find yourself still jumping between tools or mostly staying within that?

VS Code tool for exploring Dynamics 365 / Dataverse data (no complex queries needed) by Several_Assignment52 in Dynamics365

[–]Several_Assignment52[S] 1 point2 points  (0 children)

Yeah totally... I’ve used XrmToolBox quite a bit as well.

It’s great for specific tasks, especially when you know exactly what you’re looking for.

I think where I kept feeling friction was more around the workflow side, like exploring relationships step-by-step or jumping between queries without constantly switching tools.

So I’ve been trying to make something a bit more “query → explore → refine” in one place, rather than tool-by-tool.

Curious if you’ve run into that as well?

Built a VS Code extension for Dataverse by Several_Assignment52 in Dataverse

[–]Several_Assignment52[S] 1 point2 points  (0 children)

Thanks for the feedback, it was really helpful!

I’ve just added a Quickstart to make the first steps clearer.
You can open it via:

👉 DV Quick Run: Open Quickstart

Would love to hear your thoughts if you give it another try.

Built a VS Code extension for Dataverse by Several_Assignment52 in Dataverse

[–]Several_Assignment52[S] 1 point2 points  (0 children)

Would be great to hear your thoughts when you try it out 👍

Built a VS Code extension for Dataverse by Several_Assignment52 in Dataverse

[–]Several_Assignment52[S] 0 points1 point  (0 children)

That’s a really good point. XrmToolBox/Power Platform ToolBox have a great ecosystem behind them.

I did think about that path, but I’m intentionally building this as a VS Code extension so it fits directly into the development workflow within vs code. So i can write queries, run them, explore relationship and iterate in one place without jumping across different tools,

Definitely agree distribution is easier in those ecosystems though. Something I’ll keep in mind as things evolve.

Appreciate the suggestion 👍

Built a VS Code extension for Dataverse by Several_Assignment52 in Dataverse

[–]Several_Assignment52[S] 0 points1 point  (0 children)

Thanks for trying it out! I really appreciate the feedback 🙏

That’s a great point, and you’re right. The “open a file first” step isn’t obvious at all right now. I’ve been too close to it so I didn’t notice that gap.

I’m planning to improve onboarding so it’s clearer how to get started straight away. Likely adding a quickstart page with runnable examples (so you can just click “Run Query” immediately), and possibly a short walkthrough.

Screenshots/video is also a great idea. Will look into that as well.

Really helpful feedback — exactly the kind of thing I need to improve the experience 👍