A small but game-changing feature!

I’m preparing to leave my role and would appreciate practical advice on documenting the Power Apps and Power Automate processes I’ve built.

I’m an HR professional and tech enthusiast/citizen developer, rather than a professional developer. The setup has grown over time and includes:
- A Power App used by over 100 managers across the organisation for regular employee reviews and various employee lifecycle forms.
- SharePoint lists as the data sources.
- Multiple Power Automate flows, some triggered directly by the app and others supporting related processes in the background.
- One process packaged in a solution, but the majority of the setup sits outside solutions.
I’ve designed and built the entire setup myself. No technical backfill for my role is expected, and the colleague who had been learning it as a backup is also leaving.

My biggest challenge is deciding what level and format of documentation will actually be useful. I can explain how managers use the app, but handing over the underlying logic, dependencies and troubleshooting feels like a much bigger task—particularly when there may not be anyone with Power Platform experience receiving it.

For anyone who has handed over something similar:
- How did you structure the documentation? An inventory, dependency map, process guides, walkthrough recordings, or some combination?
- How far did you go into individual formulas and flow actions versus explaining their purpose and key dependencies?
- What did you prioritise around ownership, connections, permissions and keeping everything running after your account was disabled?
- Would moving the remaining components into solutions be a worthwhile handover task, or would you prioritise documenting the existing setup?
- What would your minimum viable handover contain if time were limited?

I’m looking for examples or templates that worked in practice, and anything you wish was documented before the original builder left, be that yourself as the builder, or you as the inheritor as a beginner.

I want to leave something useful and maintainable, while being realistic that documentation alone won’t replace someone having the skills and time to support it. Basically, they want to keep the lights on.

​

Hey everyone!

So I recently got hired as a Power Platform Developer, and I'm honestly excited but also a little nervous haha.

I'm a fresh IT graduate, and I worked for around 4 years as a working student assigned to our university's IT office, mostly helping faculty and staff with technical concerns and daily operations.

I also have a background in web development. I was the primary developer of our capstone project, where I worked on the frontend, backend, database, debugging, and testing using JavaScript, Node.js, Express, and PostgreSQL.

The thing is, I don't have actual professional experience with Power Apps, Power Automate, or Dataverse yet. I'm familiar with some of the concepts, but I know that working on real company projects is a completely different experience.

I was honest about my background during the hiring process, and somehow I got the opportunity! 😅

I'm willing to put in the effort to learn, but I'm also a little worried about being assigned tasks involving tools I haven't used before.

Has anyone here been hired into a Power Platform role without prior hands-on experience with the platform?

How did your first few weeks or months go? Did your company provide training, or were you mostly expected to figure things out yourself?

I'd really appreciate any advice, especially from developers who transitioned from traditional web development to Power Platform.

Thanks, everyone!

I'm pretty new to PowerApps. I've run into a bunch of weird visual artifacts in the past few weeks while working on a Canvas app, which don't always happen:

1. Outlines that sometimes don't match up with where the controls show up. Annoying but no real functional impact.

2. Mismatches in visual state between a component design view vs. the component as it sits on a screen. (Usually more after a lot of layout changes)

3. Deleting and undo-ing the delete almost always causes undeleted controls to have screwed up layouts. Sometimes undeleted controls lose some property values or get really odd values (seemingly random minimum widths and heights, or reset X/Y values, etc).

Do others experience this, and if so, is there a better fix than saving and reloading?

Hi all, with the news that PHP has a discovered a vulnerability, and urges for people to update websites or take them offline, would this have any affect on the Power Platform? Specifically Portals or Power Pages?

Hi everyone.

I wanted to share another free tool I built for canvas app makers.

The official Power Fx documentation is very good, but I often found that jumping between different references to find what I needed was tedious.

To solve this, I built an interactive A to Z mind map for the Power Apps Formula Reference. It brings the functions, syntax, and examples into one visual interface. I built this while experimenting with GitHub Copilot.

Hope it saves you some time!

Hi all,

In the app to register information and using patch for submissions. Now I want to allow user to submit multiple records in one click how will manage that. I thinking to use excel file as template but I don’t know how to figure that. Any ideas?

Thank you in advance.

Here it is, and you can click through it in your browser. No license, no sign-in, no tenant.
https://www.benschmark.eu/components/model-driven/

The video shows seven of the 68 components. The rest are in the app, each with a guide on what it is and when to use it.
https://www.benschmark.eu/components/model-driven/

What I use it for:
• Presales: show a kanban view or a business process flow without setting up an environment first.
• Workshops: let the customer click through and point at what they mean. That side panel thing becomes a quick create form.
• Onboarding: let juniors explore and learn the correct names before they touch a real environment.

Fictional data, stays in your browser. A demo for learning and showing, not a Microsoft product.

Hoping someone's seen this before because I'm out of ideas.

Power Pages site (currently on a site trial, in a paid tenant). Custom JS uses the Web API (/_api/) to create rows in a couple of custom tables, and sets a Contact lookup on create via `cr91d_Contact@odata.bind`.

`EntityPermissionAppendToIsMissingDuringAssociationChange` ("You don't have permission to associate or disassociate table contact to ..."). Makes sense, I need Append To on Contact.

the moment I save a table permission on Contact*(Self access, Authenticated Users, Append To only), the whole site goes to "We're sorry, but something went wrong" (500), including the home page, which doesn't touch Dataverse at all.

- Reverted immediately (unticked Append To, saved, clicked Sync): still 500.

- It came back on its own after ~14-15 hours.

- Tried again with just that one checkbox, nothing else changed: same thing, down again, revert didn't help, came back many hours later.

- Earlier table permission changes on other tables (Append/Append To on custom tables) were fine, no outage. It only happens with the Contact permission.

Questions:

1. Is a Contact table permission known to do this?

2. Why doesn't reverting bring the site back? Would "Restart site" in the admin center clear it faster?

3. Any way to see the real error behind the Error ID without App Insights?

4. Is there another way to set a Contact lookup from the Web API that doesn't need Append To on Contact?

Any pointers appreciated, this is a blocker

Why does Microsoft keep changing this? Does anyone know of a workaround?

I need conditional formatting on my number input fields, hundreds of them!

Am using a barcode reader in a text box field (edit form) so as scan number disappear but shows in view form

I'm interested in how others manage service accounts for CRM processes and automation.

We have a dedicated CRM service account that we've historically used to own processes and automated activities rather than running them under personal user accounts. However, I'm now unable to sign in to it, even over VPN.

• Do you use a dedicated service account or a service principal/application user?
• How do you assign classic workflows and Power Automate flows to these identities?
• How do you manage connections and permissions so automation isn't dependent on an individual employee?

I'd appreciate any real-world advice on best practice. Thanks!

Hi, I am currently developing a CodeApp with Claude and the Powerapp skills + CLI

The finished app has the complete white logo, I cant seem to find the option to change the logo for the end user on the mobile app

Claude says it is not supported in the CLI, is there really no option to change this?

Thanks!

I just noticed that Microsoft has increased the delegation limit from 2,000 to 10,000 rows. Pretty interesting and wanted to share with others.

Mudanças muito interessantes surgiram no PowerApps Modern Datagrid... Agora temos finalmente paginação de dados na tabela... E esse esquema de vc fazer um Search "semi-delegavel" (escrevendo na barra de texto da tabela a pesquisa, e ele ir paginando e buscando) vai ser uma mão na roda para nós que sempre queríamos fazer Search no SharePoint (sabemos que não é a melhor opção obviamente, mas sabendo arquitetar a formula da propriedade Items da tabela, isso já vai ajudar e servir em uns 70% dos casos)

Recentemente eu percebi também que o Datagrid está bem mais estável do que estava antes (menos bugs e mais performático), ele só está ruim ainda de usar no celular. O que acharam das mudanças no Datagrid e nas últimas mudanças do PowerApps Canvas recentemente?

Eu tinha um certo receio do Canvas se tornar algo obsoleto, porém vejo que há bastante coisa nova chegando, e isso é ótimo (pode não ser todas as melhorias que nós queríamos mas, que bom que está acontecendo)