Hello Everyone,
Today I am going to show how to turn on experimental features on Power Automate FROM Power Autmate Settings.
Let’s get’s started.
1. Login into Power Automate.
2. Click on Gear Icon
3. Experimental Features Turned ON now.
That’s it for today.
I hope this helps.
Malla Reddy Gurram(@UK365GUY)
#365BlogPostsin365Days
Hello Everyone,
Today I am going to share my thoughts on New Feature ” Create Cloud Flows using Copilot for Power Automate”.
Let’s get’s started.
Up until now, we are creating Cloud Flows using drag and drop or clicks, Now with the new feature user can give statement to the Copilot to create Cloud Flows.
Copilot in Power Automate allows open-ended and conversational experiences while authoring your flows.
While you are building flows you can ask question on Copilot and you will get assistance making improvements.
You dont need knowledge of how power automate works.
Just type in normal speaking language and you will be able to build and enhance everything from a simple to complex flows.
That’s it for today.
I hope this helps.
Malla Reddy Gurram(@UK365GUY)
#365BlogPostsin365Days
Hello Everyone,
Today I am going to share my thoughts on new features of Power Automate connect to other environments.
Let’s get’s started.
The infographic above illustrates the process of connecting to other environments using the Microsoft Dataverse connector, visually representing the integration and data exchange between different systems.
Up until now you can only use the Microsoft Dataverse (legacy) connector to connect to environments outside of the current environment.
So with this new feature, we can connect to other environments from the Microsoft Dataverse connector’s actions and triggers.
That’s it for today.
I hope this helps.
Malla Reddy Gurram(@UK365GUY)
#365BlogPostsin365Days
Hello Everyone,
Today I am going to share new feature benefits of using versioning for solution cloud flows.
Let’s get’s started.
Up until now you don’t have versioning for solution cloud flows, there is a lack of ability to revert to a previous version.
With this new feature: you can view and restore past versions of solution cloud flows, This can save your time in recreating flows when you get errors which can’t be resolve.
This ensures that business always has a working version.
Using Versioning for solution cloud flows in platforms like Microsoft Power Automate offers several key benefits that enhance the development, maintenance, and overall management of these flows.
Here are the main advantages:
1. Improved Change Tracking: Versioning allows you to keep a record of changes made overtime. This makes it easier to track who made changes, what changes were made, and when they were implemented, facilitating better change management.
2. Easier Rollback: If a new version of a flow causes issues, versioning enables you to quickly revert to a previous version that was stable and functioning correctly, thus minimizing downtime and disruption.
3. Enhanced Collaboration: In environments where multiple develpers or teams are working on the same flow, versioning helps coordinate changes and prevents conflicts. It allows for better collaboration and communication among team members.
4. Simplified Testing and Debugging: Versioning allows for the testing of specific versions of a flow.
You can identify which version introduced a bug or an issue, making it easier to debug and fix problems.
5. Audit and Compliance: For regulatory compliance and audit purposes, versioning provides a clear history of changes. This is crucial in many industries where tracking changes and maintaining records is a compliance requirement.
6. Incremental Development: Versioning supports an incremental approach to develpment, you can build and deploy flows iteratively, adding new features or improvements in subsequent versions.
7. Documentation and Understanding: Each version can be accompained by notes or documentation explaining the changes. This is valuable for new team members or when returning to a flow after some time, as it helps in understanding the evolution of the flow.
8. Confidence in Production Deployments: Versioning, coupled with proper testing practices, increases confidence when deploying flows to production, as you know that any chnages can be quickly undone if necessary.
9. Experimentation and Innovation: With the safety net that versioning provides, teams can be more experimental in trying new features or approaches, knowing that they can easily revert to a previous version if needed.
Overall, Versioning is a best practise in software development, including the development of solution cloud flows. It brings structure, safety, and clarity to the process, ultimately leading to more robust and reliable flows.
That’s it for today.
I hope this helps.
Malla Reddy Gurram(@UK365GUY)
#365BlogPostsin365Days
Hello Everyone,
Today I am going to share my thoughts on new feature Manage unpublished solution-aware cloud flows using admin APIs.
Let’s get’s started.
Managing unpublished solution-aware cloud flows in Microsoft Power Platform using admin APIs involves a sequence of steps requiring administrative privileges.
First ensure you have necessary permissions typically as a Power Platform or Global Administrator.
Access the Power Platform Admin API, which might involve registering an application in Microsoft Entra ID for authentication.
Use the API to list and identify unpublished cloud flows within a specific environment or solution,
filtering based on their publication status.
With the API, you can perform various management tasks such as updating exporting, importing or deleting these unpublished flows.
For more advanced management, Consider using Power Platform PowerShell cmdlets for a scriptable interface, allowing for easier automation.
It’s crucial to test any management scripts in a non-production environment first and monitor the changes for auditing purposes.
Additionally, staying updated with API changes is important to ensure continuous effective management of your cloud flows.
Currently, Power Automate admin APIs don’t fully support the management of solution-aware cloud flows because flows that have never been published(turned on) aren’t visible.
Power Automate admin APIs can now fully support the management of solution-aware cloud flows using
Power automate management connector
Power Automate for Admins Connector
PowerShell for Power Platform Administrators
Power Platform admin center
Admins can see unpublished solution cloud flows, share solution cloud flows and view the ownership cloud flows.
That’s it for today.
I hope this helps.
Malla Reddy Gurram(@UK365GUY)
#365BlogPostsin365Days
