How to design solutions - Revision history

CarinaMClaesson at 19:24, 12 January 2022

2022-01-12T19:24:04Z

CarinaMClaesson at 19:16, 12 January 2022

2022-01-12T19:16:00Z

CarinaMClaesson at 19:15, 12 January 2022

2022-01-12T19:15:49Z

CarinaMClaesson at 14:16, 6 December 2021

2021-12-06T14:16:19Z

CarinaMClaesson at 11:18, 6 December 2021

2021-12-06T11:18:12Z

CarinaMClaesson at 17:38, 2 December 2021

2021-12-02T17:38:30Z

CarinaMClaesson: 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..."

2021-12-02T17:37:14Z

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..."

New page

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 ===
* [[PCF]]

=== 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 ====
* [[TypeScript]]
* [[Structure of projects]]

=== Business Logic for model-driven apps ===

==== Low-code ====
* [[Power Automate]] and [[Cloud flows]]

==== 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.

@@ Line 8: / Line 8: @@
 So you think you need an app and now you need to figure out which app type to choose. Here follows some guidelines.
-* Model-driven apps have Dataverse as datasouce. Dataverse means a relational database which comes with built-in functionality for setting up security. But it also comes with a licensing cost.
+* Model-driven apps have Dataverse as data source. Dataverse means a relational database which comes with built-in functionality for setting up security. But it also comes with a licensing cost.
 * If you want to be able to have several different data sources then it might be a canvas app you need.
 * If mobility is important, then it might be a canvas app that you need.
@@ Line 18: / Line 18: @@
 == Model-driven apps ==
 This chapter contains guidance for designing model-driven apps.
 === UI extensions ===
-* [[PCF]]
+Microsoft has released the framework they use to create the UI components of model-driven apps, [[Power Apps Component Framework]]. That means, we can create (develop) our own components.
 === Business Rules ===

@@ Line 3: / Line 3: @@
 == General ==
 * Look at the requirements, what are the actual needs?
-* Have licensing in mind. Can we use Dynamics? Can we use Datverse etc.?
+* Have licensing in mind. Can we use Dynamics? Can we use Dataverse etc.?
 == Power Apps ==

@@ Line 2: / Line 2: @@
 == General ==
-* Look at the requirements, what is the actual needs?
+* Look at the requirements, what are the actual needs?
 * Have licensing in mind. Can we use Dynamics? Can we use Datverse etc.?

@@ Line 6: / Line 6: @@
 == Power Apps ==
-So you think you need an app and now you need to figure out which app type to choose.
+So you think you need an app and now you need to figure out which app type to choose. Here follows some guidelines.
 == Data Modeling with Dataverse ==

← Older revision		Revision as of 11:18, 6 December 2021
Line 1:		Line 1:
−	~~This~~ page ~~gathers~~ information about choosing the right technology.	+	You might think that you need an app, but should you choose a model-driven app or a canvas app? You know that you need some business logic to be implemented, but how do you choose the way to implement the business logic when there are so many different possibilities and ways to design and build a solution? On this page, we've tried to gather information about choosing the right technology.
		+
		+	== General ==
		+	* Look at the requirements, what is the actual needs?
		+	* Have licensing in mind. Can we use Dynamics? Can we use Datverse etc.?
		+
		+	== Power Apps ==
		+	So you think you need an app and now you need to figure out which app type to choose.

	== Data Modeling with Dataverse ==		== Data Modeling with Dataverse ==

← Older revision		Revision as of 17:38, 2 December 2021
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]]