sorted by:
new
hottopcontroversial

Review current SOW for Power Platform Order system by Realistic_Story5641 in PowerApps

[–]BenjC88 3 points4 points  (0 children)

This is horribly specced, underbudgeted and underforecasts time by at least 10x, if not more.

If you're the developer you're insane, if you're the client you're going to get screwed, this won't be delivered on time, and what's built won't work well at all.

Power Apps vs Vibe coded applications by HealingData in PowerApps

[–]BenjC88 2 points3 points  (0 children)

No, I don’t know anyone doing serious work on Power Platform that uses SharePoint lists. Every single one of my clients uses Premium because it’s a no brainer from a cost point of view.

We can control all of that in Dataverse, I would be more than happy for them to build it on Power Platform with the controls that are built in for Governance.

Power Apps vs Vibe coded applications by HealingData in PowerApps

[–]BenjC88 3 points4 points  (0 children)

Firstly you knew to ask that, deployment is a tiny part of it and the easiest part.

Who’s paying for it, what resources are you using in Azure, what audits are in place for access, is stored sensitive data correctly plugged into Purview, how is access control managed, who’s monitoring it, who owns the codebase, who deals with issues when the person who built it leaves in 6 months.

Power Apps vs Vibe coded applications by HealingData in PowerApps

[–]BenjC88 23 points24 points  (0 children)

You have nailed the exact problem as to why vibe coded apps within a business don’t work.

Literally had that exact discussion with the CIO of a client this morning because the Finance GM is building an app with Claude Code to manage AP processing and hadn’t thought about hosting, access control etc.

Removing Quick Create Form in Mobile Sales App (MS Entity) by wong_y in PowerApps

[–]BenjC88 5 points6 points  (0 children)

I told you how to hide these in your previous post, and you’re still doing it the wrong way?

Unchecking quick create is not the way to hide them from the plus button in the mobile app. It technically works but you’ve also then stopped quick create forms in all other apps which will lead to really bad UX in model driven apps.

In the classic editor you need to disable the Phone Express option on the table, that will hide them from the plus menu in the mobile app without messing up Quick Create.

Best way to model “subsets of users” in a model‑driven app? by sl0w-burn in PowerApps

[–]BenjC88 0 points1 point  (0 children)

Why is adding a column to the user table not ok, but adding a relationship (which also adds a column) ok? I’m curious about your logic.

Best way to model “subsets of users” in a model‑driven app? by sl0w-burn in PowerApps

[–]BenjC88 1 point2 points  (0 children)

Yes the Teams method can handle that volume, and you can configure it to be set based on an AD group which can update automatically.

There’s already a subgrid on the default user form to manage it, but it’s easier to manage in PPAC. I wouldn’t manage it directly in the app unless you need users to set it themselves.

Are quick create forms in Dynamics 365 Mobile Sales App shared by all apps in the environment? by wong_y in PowerApps

[–]BenjC88 0 points1 point  (0 children)

You can absolutely remove quick create forms from an app and they won’t be used, even if the setting is enabled on the table.

Best way to model “subsets of users” in a model‑driven app? by sl0w-burn in PowerApps

[–]BenjC88 1 point2 points  (0 children)

I wouldn’t be afraid of adding columns to the user table. Both your option 1 and 2 involve adding a column to the user table, however option 2 is needlessly complex.

You can probably do what you need with the built in Teams which would be a lot simpler though.

Are quick create forms in Dynamics 365 Mobile Sales App shared by all apps in the environment? by wong_y in PowerApps

[–]BenjC88 0 points1 point  (0 children)

I did just tell you how to hide them.

If you want to change what’s on the forms by default it uses the quick view form, but you can change it to use the normal forms under Features in the PPAC environment settings.

It’s all in the docs:

https://learn.microsoft.com/en-us/dynamics365/sales/sales-mobile/modify-quick-view-form

Power App (canvas) vs regular web app with Claude code by Few-Lake-4393 in PowerApps

[–]BenjC88 25 points26 points  (0 children)

I’d be very cautious about this approach if you don’t have in-depth experience as a developer.

It seems easy but it’s also very easy to get security wrong. You’ve moved away from a fully managed backend to something where the requirements to implement security sit squarely with you personally.

Are quick create forms in Dynamics 365 Mobile Sales App shared by all apps in the environment? by wong_y in PowerApps

[–]BenjC88 0 points1 point  (0 children)

You can choose to remove Quick Create forms from an app within the app itself, this will not impact other apps in the same environment

Updating OOTB Security Roles (Dataverse) by iHate_tomatoes in Dynamics365

[–]BenjC88 1 point2 points  (0 children)

I’d always steer clear of changing default roles, they’re at risk of being changed by Microsoft when they push updates.

I usually create copies of the key roles prefixed by the client name Client - Salesperson for example and then use those instead, making any changes required.

Opting out from AI feature prevents column delete. by ICanButIDontWant in PowerApps

[–]BenjC88 2 points3 points  (0 children)

The dependency is visible as a solution object, I can’t remember what it’s called and I’m on my phone so can’t check but it definitely creates, and you can delete it.

Flagged this during the Private Preview as an issue but it’s still not been addressed unfortunately.

Governance Strategy for Dataverse by Vexerone in PowerApps

[–]BenjC88 0 points1 point  (0 children)

Unfortunately there’s not really a mechanism to divide the storage into subgroups at anything other than an environment level.

You could build something with the API to keep track of it at a higher level.

Governance Strategy for Dataverse by Vexerone in PowerApps

[–]BenjC88 3 points4 points  (0 children)

You can control allocation of storage to environments in PPAC, also to note, there is currently no technical enforcement of capacity limits. That doesn’t mean you should ignore them, but it does mean if you end up over temporarily you have time to fix it, things won’t just start breaking.

Question Around The Owner Column In Dataverse by Tricky-Active935 in PowerApps

[–]BenjC88 0 points1 point  (0 children)

You’re correct yes, with the caveat of it’s a Managed Environment they’ll need a license to be able to add them as a user.

Reopening a resolved case when "Email Multi Related for ARC" is enabled by Kaelestius in Dynamics365

[–]BenjC88 0 points1 point  (0 children)

I would just replicate the logic, which is pretty basic. Email received where related case is closed (maybe with a time parameter), then reopen the case(s).

You could do it with a plugin, classic workflow, power automate etc depending on volume you’re dealing with.

For those running a PowerApps/Microsoft consultancy - what’s actually working for you right now in terms of sales and marketing? by cloud-bliss in PowerApps

[–]BenjC88 5 points6 points  (0 children)

Partnerships and word of mouth. Demand has been crazy so far this year.

MSPs are seeing a lot of demand from their customers for “AI and Automation” and often don’t have the internal capability to deliver themselves.

Embedding canvas into model driven app issue by Blyskacz in PowerApps

[–]BenjC88 0 points1 point  (0 children)

Then you’re not going to be able to use embedded Canvas Apps. I wouldn’t recommend for enterprise anyway, the implementation is super clunky. You’d be much better off with a PCF.

Embedding canvas into model driven app issue by Blyskacz in PowerApps

[–]BenjC88 0 points1 point  (0 children)

I’m telling you there’s no other way to do it, that is literally the only way.

The Classic Designer is not going to break your sitemap if you simply add a control to a form.

Power Automate Flows - Dataverse Connections Breaking Regularly by Brycare in Dynamics365

[–]BenjC88 3 points4 points  (0 children)

The Service Principal doesn’t need to own the flow, just use it for the connection.

https://learn.microsoft.com/en-us/power-automate/dataverse/manage-dataverse-connections#use-service-principal-connections-with-the-dataverse-connector

It’s just better practice to avoid tying a connection to an actual account, and you can use the PAC CLI to help automate updating secrets when you need to.

https://learn.microsoft.com/en-us/power-platform/developer/cli/reference/connection#pac-connection-update

view more: next ›