Share
ReportHi all!
I'm having an issue with editing a save button in the editor mode for one of my apps. I've built an app on top of Microsoft's Dataverse and have ~15 tables with forms that I edit on one page. Only one table's forms are present at a time, and the forms visibility is dependent on ~15 different buttons selected on a previous screen.
My issue is that the Save button I have on the screen with my ~15 table forms has become very large. Right now I only have one save button control that has a switch statement in the OnSelect property that saves any of my ~15 tables' form depending on what button was pressed on my previous screen. I have to do a lot of different operations when someone saves a form, and since there's ~15 tables the code is basically ~15 as long as if I used one save button per form/table. This results in my save button taking forever to edit, as I have to wait minutes for the changes I type to actually register and become visible in the app.
My main question is this: should I split this 1 save button into ~15 different save buttons? Would this make editing the save button easier? Or would the increase in number of controls in one screen be too much and cause my app to still be slow while editing?
Let me know if any clarification is needed.
Thanks!
All responses (
Answers (
58
