| Mustafa Usmani
You might’ve seen this phrase whenever you’re going through Power Platform’s Licensing and must’ve wondered what does “within context of the app” actually means and how does it affect your usage of license in the Platform. In this blog, let’s try to understand that.
So, we can say that a for a flow to be “within context”, it has to be using the same data sources for triggers or actions when it comes to the model-driven applications used data sources. For example, if my created model driven app is using Accounts and Contacts table. The flow has to have trigger or actions that are using the same table.
But that does not mean I cannot use non-Dataverse actions in that flow. I can still benefit from other connectors or other data sources as well, but the key point here is that there has to be trigger or actions of the Dataverse connector using the tables that I have used in my application.
An example of a flow not being within context would be: When a mail arrives and you process the information in it using an Azure function and sending it to SharePoint. Or another example can be of using PowerBI connector and send a report through the email. Now techincally, the PowerBI would be using the Dataverse tables for the report generation but the flow isn’t using those tables in its context.
Join us next time, as we continue our journey of learning canvas apps.Click here to learn more about Imperium's Power Apps Services. We hope this information was useful, and we look forward to sharing more insights into the Power Platform world.
