Azure Logic Apps
|Power Automate is built on top of Azure Logic Apps|
|It is a SaaS service for workflow automation across several different apps and SaaS services.||It is a PaaS service for workflow automation across several different apps, SaaS services, and IaaS services for enterprise integration.|
|For more of self-service and simple integration scenarios.||For complex/advanced integration scenarios|
|Targeted for Business User, Citizen Developers, Developers, IT Pros.||Targeted for Developers and IT Pros.|
|Brower based designer and mobile app UI only
||In-browser as well as Visual Studio|
|Office 365 Service / License / Subscription||Azure Service / License / Subscription|
|Flow specific Connectors||Logic App-specific Connectors – SAP, IBM MQ, IoT, Liquid.|
|Power Automate are specific to an environment||There is no environment concept, each logic app is an independent entity.|
|Pay by run||Pay by action run and by connector run.|
|Flow can be extended as Logic Apps
|Power Automate is supposed to be designed and tested in a non-production environment and then promoted to the production environment. The solution makes it possible with connectors requiring reconfiguration. Connection references can be considered here https://flow.microsoft.com/en-us/blog/move-flows-across-environments-without-resetting-connections/
||Logic Apps has ALM possibilities.|
|Admin Experience through Power Platform Admin Center.||Admin experience through Azure Portal.|
While trying to connect to a table within Azure Data Lake Storage Gen2 through CDS Folder View
we got the below error
Users have reported this issue with the August 2020 Update of Power BI Desktop.
Hope it helps..
While trying to connect to Azure Data Lake Storage Gen2 through Power BI Desktop we got the below error
Came as surprise cause the user was had the owner role assigned to the container
It turned out we need to assign the Storage Blob Data Reader role to the user.
After assigning the role we were able to connect successfully.
Hope it helps..
Azure Data lake store gen 2 can be described as a large repository of data, structured or unstructured built on top of Azure Blob storage, that is secure (encryption – data at rest), manageable, scalable, cost-effective, easy to integrate with.
- Export to Data Lake allows for continuous replication of CDS entities to Data Lake Storage Gen2, which involves initial write followed by incremental writes, which can be consumed by Power BI, Azure Data Factory, Azure Data Bricks, and Azure Machine Learning.
- Replication of standard and custom entities having change tracking enabled and create, update, and delete operations.
- Any changes in data and metadata are pushed automatically without the need of setting any refresh intervals.
Let us first create a general-purpose V2 storage account to access all of the Azure storage services like blobs, files, etc.
The storage account must be in the same Azure AD tenant.
Login to Azure Portal (with admin account)
Search for Storage Accounts.
Here we have used a trial to create the storage account.
Leave the Account kind, Replication, and Blog Access as the default values while creating the storage account.
Before selecting Review + Create, navigate to the Advanced tab and enable the Hierarchical Namespace.
After validation is done and is successful, click on Create to create the storage account.
With the storage account created successfully, navigate to PowerApps select the option Export to data lake.
Select New link to data lake
Specify the storage account created earlier.
Select the entities to be exported to the data lake. Enable change tracking for the entities, as only these entities will be exported.
Clicking on save will link the CDS environment with Azure data lake storage.
It will create the file system in the Azure storage account having a folder for each entity selected.
and will start the initial sync.
we can use the Manage entities option for adding or removing the linked entities.
Inside Azure Portal, we can navigate to the storage account and select the Storage Explorer.
container to view the details.
The CSV file will contain the data
Here Model.json is the metadata file in the CDM folder
that describes the data in the folders, metadata, and location.
Hope it helps.
Check it out, the column comparison feature is now added in our favorite XrmToolBox plugins (make sure to update to the latest version)
- FetchXML Builder
- SQL 4 CDS
Also, refer –
Hope it helps..
Recently a new Trial (subscription-based) environment option added to the tenants in the Power Platform Admin Center
Earlier we were limited to below options –
These new trial types are created and controlled by tenant administrators, as a result of signing up for a trial subscription and can be added to the existing tenant.
This new environment follows the trial subscription lifecycle (which is typically 30 days) and can be extended from the admin center.
- A total of 3 trial environments can be created.
- Trying to create 4th will give us the below error
Get more details here
Hope it helps..