r/PowerPlatform

Hi everyone,

Is anyone else experiencing strange issues with Dataverse / Dataverse plugins since this morning?

Specifically, it looks like Dataverse may be returning or expecting the Schema Name instead of the Logical Name for some attributes inside plugins. This is breaking late-bound logic that expects column logical names.

Example:

var value = entity.GetAttributeValue<string>("new_customfield");

where new_customfield is the logical name. Since this morning, in some scenarios, it looks like something like new_CustomField — or the schema name equivalent — is being returned/required instead, causing null values, missing attributes, or unexpected plugin behavior.

This seems odd because, according to Microsoft’s Dataverse SDK documentation, late-bound code works with logical names. For example, Entity.LogicalName, AttributeCollection, GetAttributeValue<T>(), IOrganizationService.Retrieve, and metadata properties such as LogicalName are all based on logical names rather than schema names.

Context:

• Dataverse plugins in C#
• late-bound entities using Entity, Attributes, and GetAttributeValue<T>()
• attribute names no longer seem to match what the plugin expects
• no code changes on our side
• behavior appears to have changed suddenly this morning

Has anyone else seen this today?

Does anyone know whether Microsoft has rolled out an update, regression, or undocumented breaking change affecting Dataverse / Power Platform plugins?

Any workaround or confirmation would be appreciated.

Thanks!

In my company, and in many others, low-code solutions are spreading rapidly. Despite the growing demand, I feel that the company doesn’t take low-code development seriously. They see it only as something “extra,” almost like a part-time responsibility. Having to work on this in my “free time” is really frustrating because I’m never 100% focused on the solutions and architectures, and I end up losing track of some aspects of the work.

Furthermore, nowadays it seems like everyone is a citizen developer. With new tools like Copilot and vibe coding, everyone is creating solutions, which makes me wonder: “Is my development work still necessary?”

At times, I feel like I could be fully dedicated to low-code development and focus entirely on building solutions, but I increasingly find myself questioning the future of low-code development.

Between this and being a technician who works with SQL, Java, MES.. I don't know which would be better for the future.

Hello everyone,

Some folks, and maybe admins, might see this post as bragging but I hope you'll let me share my achievement nonetheless.

I first laid hands on powerapps as an intern in 2016. From there, my boss made me explore it when I started my first job in 2018.

I didnt study CS or anything like that in Uni, so this was all new to me. Since then its been 8 years of working on powerplatform, building solutions for my company and our clients. And at some point I started lurking on this sub and r/powerplatform, just seeing what the community is up to.

Throughout that time, Power Platform adoption was slow in my country. Jobs and opportunities didnt come by too often. Many times I thought about switching to some other career path. Im glad I didnt. Because next week, after 8 years, I start at Microsoft.

The role is a pretty respectable one and I am beyond stoked. It may not be much of an accomplishment to most people, but coming from a non-IT background, working at Microsoft was a career ambition of mine that felt unattainable for so long.

Anyway, thanks for reading this far. I hope PowerPlatform has been and will continue to be as rewarding to you guys as it has been to me 🫡

Edit: I realised I forgot to mention that I'm actually really nervous to start next week and writing this post was my wife's suggestion to calm my nerves 😅

Are you using Power Apps code apps in your organization? What’s your experience been like with integrating the Graph API? Interested to hear your thoughts, challenges, and best practices.

We want Agent Builder broadly available but Copilot Studio limited to a smaller, trained cohort (possibly long-term). The catch is an existing Citizen Development program running in its own default environment that we don't want to disturb.

Has anyone done this cleanly and consistently? Security groups, environment routing, DLP, licensing. What's worked?

Background: when we gave end users the full PP experience out of the gate, adoption and support became a real burden. Trying not to repeat that.

Most Nintex migrations become difficult not because of the platform itself, but because old workflows often contain years of layered fixes and undocumented logic.

The smartest teams usually treat migration as an opportunity to simplify and clean up workflows first, then migrate what still delivers real business value.

Once the unnecessary complexity is removed, the actual transition becomes far more predictable and easier to manage.

I have a few different clients that I've build apps for contacting me saying nothing is working. I can't see any issues from MS on the service health for PowerApps, but when I live monitor one of the apps every request is failing with 520 "API Hub token exchange internal server failure"... feels like a wider issue... Is anyone else seeing issues?

• Ctrl + N - Create a new Power BI file

• Ctrl + O - Open an existing Power BI file

• Ctrl + S - Save the current report

• Ctrl + Shift + S - Save As

• Ctrl + P - Print report

• Ctrl + Z - Undo last action

• Ctrl + Y -Redo last action

• Ctrl + C -Copy selected visual/object

• Ctrl + V - Paste copied visual/object

• Ctrl + X - Cut selected item

• Ctrl + A - Select all elements

• Ctrl + F - Find/Search in report

• Ctrl + Shift + F -Open filter pane search

• Ctrl + Click -Multi-select visuals

• Delete - Remove selected visual/object

• Esc - Cancel current action

• F1 - Open Power BI help

• F2 - Rename selected field/object

• F5 - Refresh report

• Ctrl + R - Refresh visuals/data

• Alt + Shift + F10 - Open context menu

• Shift + Arrow Keys - Select multiple items

• Tab - Move to next object

• Shift + Tab - Move to previous object

• Arrow Keys -Navigate between visuals

• Alt + Shift + Up Arrow - Move visual up

• Alt + Shift + Down Arrow -Move visual down

• Alt + Shift + Left Arrow - Move visual left

• Alt + Shift + Right Arrow - Move visual right

• Ctrl + Mouse Wheel - Zoom in/out on report canvas

Are you exploring Power Apps Code Apps for more advanced scenarios? What type of apps are you building, and what challenges have you faced so far?

Built an M365 FAQ App using Power Apps Code Apps (React + Vite + PAC CLI) to create a richer and more flexible UX than traditional Canvas app layouts.

What surprised me most: PAC CLI auto-generates the typed service layer directly from the SharePoint schema — no manual API calls, auth handling, or token management.

Power Apps Code App FAQ App

https://reddit.com/link/1tas7pq/video/6yeqa9478n0h1/player

Note: No selling purely for community sharing 😄

Features:
• Real-time search with term highlighting
• Markdown-rendered answers
• Dynamic category filters from SharePoint
• Accordion + modal view modes
• Fully responsive design

Backend: SharePoint as a headless CMS.

The full project is open source, and I’ve shared the repo and architecture guide in the comments.

So…we’ve had the same Power Platform developer in post for a very long time, and they’ve just retired. Most of their work was done in a dedicated account for Power Apps, Power Automate, etc. so when they left it just carried on. However early stuff was in their own account - which obviously then broke when their account was off boarded…which gave the new hire some tasks for their first couple of weeks 🤣

But with my Cyber Security hat on the “shared” account for all Power Apps, connectors, flows, etc. also has me worried…shared creds = bad.

So I’m wondering what is the done thing in Power Platform world so Apps don’t break if the developer account is disabled/deleted/password changed. But also better security than just a shared account logged in via their In Private browser mode.

Also interested if the same applies for PowerBI and the account which owns the refreshes of the semantic models?

In our Power Automate environment, we are having massive issues with flows that contain SQL Connections, or are complex flows.

Here are a list of issues we are experiencing:

- Out of Memory (Microsoft Edge). The browser window shows "This page is having a problem". It usually appears a few minutes after the flow has loaded.

- Invalid Parameters. This is showing on all SQL Server flows.

- Variables have lost their inputs, resulting in failed flows.

- SQL Server Name and Databases are defaulting to "Default" and not the server name or database name.

So as it stands, we cannot edit flows or fix them.

This is a known issue in PowerAutomate - accessible at: 6356365 | Power Platform admin center

Microsoft say the fix is deploying to environments which make take WEEKS!

If you're hitting SNAT port exhaustion or auth bottlenecks in high-load Dynamics 365 integrations, creating a new ServiceClient() per request is likely why. I just published a full breakdown on the Microsoft Mission Critical blog on how to fix this using _baseClient.Clone() for thread-safe, lightweight requests. Check it out!

Hi Redditors,

I wonder if the collective knowledge of this community can point me to the best path to start learning 🎓 Power Automate ⏩.

I have 5 years of experience in analytics, am PL-300 certified, and have some ideas for implementing in my current role. I would like to streamline and automate a quarterly data-readiness and data-validation process for a monthly reporting cadence, combining Power BI and Power Automate.

I appreciate any recommendations and best practices you can share 🤗

Hey everyone,

I'm building a model-driven app (FAQ/info hub) backed by Dataverse for a store chain with multiple locations. The requirement is simple: everyone can read everything, but employees should only be able to edit records belonging to their own store.

After researching this, it seems like the "correct" approach is:

1. Create a Business Unit per store
2. Create an Entra security group per store
3. Link them together as Dataverse group teams
4. Assign a security role with Read = Organization, Write = Business Unit
5. Migrate all existing records to the correct Owning Business Unit

And every time a new store opens, repeat steps 1-3 again.

It works, I get it. But coming from Power BI where you can set up RLS with a simple DAX filter like [Store] = USERPRINCIPALNAME() or look up the user's location from a mapping table, this feels really heavy for what's essentially the same problem.

I wish Dataverse had something similar where you could define a security rule that says "match this column to a user profile attribute" without having to spin up new BUs, Entra groups, and group teams every time a location is added.

So my questions:

• Is the BU-per-location approach really the standard for this? Or is there a more dynamic/scalable way?
• Has anyone used row-level security or plugins to achieve something more flexible?
• For those managing something similair, how do you handle the overhead of creating new BUs + Entra groups every time?
• Any thoughts on automating this with Power Automate or the Dataverse API to make it less painful?

Would love to hear how others are solving this. Thanks!

Hi all,

I have been working in Power Platform for a few years now and the last couple of days I can not seem to get some work done. Everytime I load a flow (not overly complex) it is painfully slow and when I try to add a new action/step I get the message wait/force close.

This makes it impossible to correctly adjust or extend my flows.

I tested this on multiple environments and also on multiple networks/computers/browsers.
At first I thought it was because of my transition to a Macbook but my Windows device has the same problem.

Any other persons who are having the same issue?

Hi all, anyone here attended a Power Platform interview at EY? Would appreciate if you could share your experience, questions, and suggestions.

We’ve been running most of our internal processes through SharePoint, and over time it turned into a mix of quick fixes, workarounds, and “temporary” workflows that stuck around.

So I spent about 90 days trying to clean things up and automate some of our most common tasks.

Big takeaway: the hardest part wasn’t building workflows, it was figuring out what actually should exist. A lot of time went into removing outdated steps, simplifying processes, and getting clarity on what people really needed.

Once we did that, adoption improved and things started running smoother with fewer missed steps and follow-ups.

It changed how I think about automation, sometimes the real work is cleaning up before you automate anything.

Curious if others had a similar experience when trying to improve internal workflows?