Difference between revisions of "How to design solutions"
Jump to navigation
Jump to search
(Created page with "This page gathers information about choosing the right technology. == Data Modeling with Dataverse == == Model-driven apps == This chapter contains guidance for designing mo...") |
|||
| Line 32: | Line 32: | ||
==== User Notifications in model-driven apps ==== | ==== User Notifications in model-driven apps ==== | ||
[[In-app notifications]] give the user notifications within the model-driven app and these notifications can be seen when using the app. | [[In-app notifications]] give the user notifications within the model-driven app and these notifications can be seen when using the app. | ||
| + | |||
| + | [[Category:How-To]] | ||
| + | [[Category:Developer]] | ||
| + | [[Category:Maker]] | ||
Revision as of 17:38, 2 December 2021
This page gathers information about choosing the right technology.
Data Modeling with Dataverse
Model-driven apps
This chapter contains guidance for designing model-driven apps.
UI extensions
Business Rules
Business Rules can be used e.g. in order to set a column as mandatory or hide/display a column depending on some certain logic. Used for more simpler form logic/manipulations.
Form Scripting
When you reach limitations in Business Rules (e.g. you need to hide/show a column based on the value of a related table's column) developers can use JavaScript to implement the form logic.
TypeScript
Business Logic for model-driven apps
Low-code
Develper
- Plugins Some examples are validation, data manipulation, integration
- (Custom) Classic workflows
- Azure Functions
Other
User Notifications in model-driven apps
In-app notifications give the user notifications within the model-driven app and these notifications can be seen when using the app.