The OnSave event in Model-Driven Forms was one of the events where we couldn’t execute asynchronous code, and that stayed that way for a very long time. The only way we could make some requests before saving a record, was to stop the saving process, make the requests and start the saving again. But that had some other issues, because that would reject any formContext.data.save() attempts, written behind some standard ribbon commands.
A few years ago, we’ve got the “ Async OnSave “. This is an option, we can set for each Model-Driven App
Microsoft Power Apps is a low-code platform that allows users to create custom business applications for web and mobile devices without requiring extensive programming knowledge. Within Power Apps, Model-driven apps are a specific type of app that use a data model to define the app’s user interface and business logic.
Model-driven apps in Microsoft Power Apps are built on top of the Common Data Service (CDS), which is a cloud-based storage service that allows users to securely store and manage business data. The data model used by the app is defined in the CDS, which allows developers and users to create and customize tables, fields, and relationships.
Using model-driven apps, users can create custom forms, views, and dashboards that are based on the data model. The app’s user interface is automatically generated based on the data model, making it easy to create consistent and visually appealing apps. Additionally, model-driven apps come with built-in business logic that can be customized to meet specific business requirements.
Model-driven apps are ideal for complex scenarios that require data modeling and business logic. They are commonly used in industries such as healthcare, finance, and manufacturing, where complex data relationships and business rules are common. Model-driven apps can be accessed from web browsers or mobile devices, and they can be integrated with other Microsoft and third-party applications.