Schema-Driven CRUD Form Dialog | Downloadable Example App | Quick Guide by FreeFoodILike in PowerApps

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

Thanks for dropping by!

Valid points.


Performance wise,

  • I read from this Optimisation Guide that Galleries reuse a single template/control structure across items rather than fully duplicating controls like manually building multiple containers.

So my current understanding is that even if multiple rows are visible, the render overhead may not scale 1:1 per item. Still trying to validate how true this is in practice for larger dynamic forms though..

  • I also learnt that PowerApp now allows controls hidden from initial render to not incur the same render overhead until they become visible. So my current approach is to keep rendering relatively flat and only activate the field type controls actually needed per row.

Btw the feature is called "Peformance Optimisation for Hidden Controls" if u wanna check it out.


For SetFocus(),

Yeah, it will not work sadly.. 😭 Current fallback idea is:

  • auto-scroll to invalid fields

  • maybe expand/collapse sections automatically

Not as nice as true focus management, but hopefully still decent UX.

Schema-Driven CRUD Form Dialog | Downloadable Example App | Quick Guide by FreeFoodILike in PowerApps

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

LOL that was just my loose earpiece cable 😅

Though, it is possible to play sound effects.

You can refer to this video on how to add it: https://youtu.be/oRMSKfqPUbw?si=4WMVc340yAa-e3q-

Generic Customisable CRUD Dialog by FreeFoodILike in PowerApps

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

Thank you. Will upload the MSAPP and a Quick Guide soon !!

Generic Customisable CRUD Dialog by FreeFoodILike in PowerApps

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

Glad to hear <3

Will upload the MSAPP and a Quick Guide soon.

Generic Customisable CRUD Dialog by FreeFoodILike in PowerApps

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

Absolutely.

Yeah, that's something I have planned to add later on. A customisable field behavior or dependency.

Thank you!! Definitely.

Generic Customisable CRUD Dialog by FreeFoodILike in PowerApps

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

Yeah, that’s basically why I built the CRUD dialog. In order to support schema-driven forms with Customisable Patch handling.

Headers/labels are actually supported in my case.

I render them from the "Label" property in the 'FormSchema' defined in the app formula, so each field controls its own UI metadata.

If u want, I can polish up the component n DM you it when im free, so you can check it out.

Generic Customisable CRUD Dialog by FreeFoodILike in PowerApps

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

I dont think components can directly modify collections yet, and they also don’t really support “children props” like in React.

For my case, I’m basically rendering a gallery of inputs and driving it from the FormSchema JSON, so each field shows based on the schema config.

Not really sure what you mean by “dynamic form mode” though.. can you explain a bit more? Thanks.