cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
Sven_Rahn
Regular Visitor

Power Platform Build Tools: Connection reference

Hi!

So we successfully implemented ALM with some Azure DevOps Pipelines and the official Power Platform Build Tools. But there's one problem:

When importing a solution which contains a Flow and its connection reference, it doesn't update itself correctly and just turns itself off.
It is as if I would import the solution with the old solution explorer UI. The new PowerApps solution UI asks when importing to update the connection references. But the old UI and the Power Platform Build Tools in Azure DevOps just disable the Flow.

So after having everything automated, we still have to go into the prod environment and update each connection reference and activate each Flow (even if it didn't change). I guess the process is worse now than without ALM.

Are there any workarounds or possibilities to use the "new UI" import API? Or am I missing something? How should this be handled with ALM?

15 REPLIES 15

Hi Sven,

 

While not truly automated, I have found that if a flow has already been configured (connections resolved) using the new import solution experience in the target environment, then subsequent solution imports of that flow (manually or via a pipeline) will keep the flow state as 'On'.

 

So in summary:

  • Import the flows solution manually and configure in the target environment
  • Subsequent solution imports with the same flows should keep the flows state as 'On'

This however isn't ideal when you are introducing a new flow to the target environment for which would need to follow the above process again.

 

Hope this helps,

Ryan

drivard
Advocate II
Advocate II

Hi,

 

You might want to have look at this gist from Marc Schweigert of Microsoft.

https://gist.github.com/devkeydet/f31554566b2e53ddd8e7e1db4af555a6 

 

It explains the current limitation and a possible workaround. I haven't tried it yet though.

 

Another possible avenue that I can think of (while not fully automated, and far from ideal I agree)

- Remove the connection references from your main solution and put them in a separate solution.

- Install the connection references solution manually in the target environment using the new UI and update the connections (these should not change very often)

- Now your automated deployments should not turn off the flows on every release

 

Hope this helps,

 

 

 

Sven_Rahn
Regular Visitor

Thanks for the suggestions!

I imported the connection references into the other environment and changed it accordingly to have the right connection. The logical name of the connection reference in dev and prod are the same.


But still when I import the Flow with the pipeline it always disables the Flow. I did the first import manually and the second import with the pipeline via an app user. All imports by the app user disable the Flow.

 

I am pretty sure this is because the connection used by the Flow is not owned by the App user but by the "normal" admin user account. If the owner of the connection would be the app user I guess it would work. But I don't really see a way to change the owner of the connection. The connection doesn't seem to be a really accessible record.

See this https://community.dynamics.com/crm/b/crminthefield/posts/using-connection-references-with-power-auto...


So, the pipeline has to use the same user as the owner of the connection. In the pipeline I can only use an app user because of MFA. But then I need a way to set the owner of the connection.

Is Microsoft aware of this issue?

Edit: I was able to import the Flow by impersonating the owner of the connection in the XRM Toolbox, and the Flow wasn't disabled. So it worked! But I can't see a way to impersonate another user with the Power Platform Build Tools sadly.

ScottDurow
Memorable Member
Memorable Member

The workaround I use for this is to have a script in my pipeline that impersonates the owner of the connection and turns on all the flows that uses that connection.

hi, Scott

Would you please show how can we use the script in pipeline to impersonates the owner of the connection and turns on all the flows ?  Can you provide a script snap shot ? 

Thanks. 

Hi Scott,

 

I would like to see the script as well.  Would save a TON of time.

@ScottCostello/@stone_haha,

 

You can activate/switch on cloud flows from an Azure DevOps pipeline using PowerShell while impersonating another user. i.e. the owner of the cloud flows for example. See below, a sample script for doing this.

 

 

$headers = New-Object "System.Collections.Generic.Dictionary[[String],[String]]"
$headers.Add("CallerObjectId", "c85463fb-XXXX-XXXX-XXXX-3c73fc279d03")
$headers.Add("Authorization", "Bearer eyJ0eXAi...")
$headers.Add("Content-Type", "application/json")

$body = "{ 'statecode': 1, 'statuscode': 2 }"

$response = Invoke-WebRequest -Uri 'https://XXXXXXXX.crmX.dynamics.com/api/data/v9.2/workflows(bc9d6d8f-XXXX-XXXX-XXXX-000d3ab8a215)' -Method 'PATCH' -Headers $headers -Body $body

$response.StatusCode
$response.StatusDescription

 

 

Some notes on the above:

  • The CallerObjectId header should be the object ID of the AAD user you want to impersonate - Impersonate another user
  • You need to pass in a Bearer token in the Authorization header - See Use OAuth authentication with Microsoft Dataverse
  • statecode and statuscode of 1 and 2 respectively represent an Activated workflow - See Workflow table/entity reference
  • You need to update the Uri parameter of Invoke-WebRequest to use your environments name, region, and the workflow ID.
  • Most of the parameters used in this PowerShell script could be setup as variables in the pipeline using the PowerShell script task.
  • This example only activates a single flow but the same process would apply to activating multiple whereby you could loop over a list of cloud flows and attempt to activate them. A retry pattern could be used.  

Thanks Ryanspain!

 

I've got almost all of it working accept that the Invoke-WebRequest I get an error returned saying (400) Bad Request.  Unfortunately I don't see any other information.  

 

I believe I've authenticated correctly, but something is off.

I think I have the correct WorkflowId, I got it from the WorkFlow edit Url.  

 

Could this be an issue with privileges? 

Hi @ScottCostello,

 

You would receive a 401 unauthorised if it was a privilege issue. A response code of 400 indicates a bad request which could mean a problem with the input arguements.

 

For example, using curly braces in the workflow identifier as below would result in a 400 bad request response.

 

.../api/data/v9.2/workflows({bc9d6d8f-XXXX-XXXX-XXXX-000d3ab8a215})

 

 

If everything looks ok on your end, try pasting your snippets (with sensitive info omitted) here and I'd be happy to cast an eye over.

 

Finally, I'm no export on PowerShell but I generated most of my supplied sample using a neat feature of Postman that lets me turn a HTTP request into a PowerShell script.

 

Helpful resources

Announcements

Community will be READ ONLY July 16th, 5p PDT -July 22nd

Dear Community Members,   We'd like to let you know of an upcoming change to the community platform: starting July 16th, the platform will transition to a READ ONLY mode until July 22nd.   During this period, members will not be able to Kudo, Comment, or Reply to any posts.   On July 22nd, please be on the lookout for a message sent to the email address registered on your community profile. This email is crucial as it will contain your unique code and link to register for the new platform encompassing all of the communities.   What to Expect in the New Community: A more unified experience where all products, including Power Apps, Power Automate, Copilot Studio, and Power Pages, will be accessible from one community.Community Blogs that you can syndicate and link to for automatic updates. We appreciate your understanding and cooperation during this transition. Stay tuned for the exciting new features and a seamless community experience ahead!

Summer of Solutions | Week 4 Results | Winners will be posted on July 24th

We are excited to announce the Summer of Solutions Challenge!   This challenge is kicking off on Monday, June 17th and will run for (4) weeks.  The challenge is open to all Power Platform (Power Apps, Power Automate, Copilot Studio & Power Pages) community members. We invite you to participate in a quest to provide solutions in the Forums to as many questions as you can. Answers can be provided in all the communities.    Entry Period: This Challenge will consist of four weekly Entry Periods as follows (each an “Entry Period”)   - 12:00 a.m. PT on June 17, 2024 – 11:59 p.m. PT on June 23, 2024 - 12:00 a.m. PT on June 24, 2024 – 11:59 p.m. PT on June 30, 2024 - 12:00 a.m. PT on July 1, 2024 – 11:59 p.m. PT on July 7, 2024 - 12:00 a.m. PT on July 8, 2024 – 11:59 p.m. PT on July 14, 2024   Entries will be eligible for the Entry Period in which they are received and will not carryover to subsequent weekly entry periods.  You must enter into each weekly Entry Period separately.   How to Enter: We invite you to participate in a quest to provide "Accepted Solutions" to as many questions as you can. Answers can be provided in all the communities. Users must provide a solution which can be an “Accepted Solution” in the Forums in all of the communities and there are no limits to the number of “Accepted Solutions” that a member can provide for entries in this challenge, but each entry must be substantially unique and different.    Winner Selection and Prizes: At the end of each week, we will list the top ten (10) Community users which will consist of: 5 Community Members & 5 Super Users and they will advance to the final drawing. We will post each week in the News & Announcements the top 10 Solution providers.  At the end of the challenge, we will add all of the top 10 weekly names and enter them into a random drawing.  Then we will randomly select ten (10) winners (5 Community Members & 5 Super Users) from among all eligible entrants received across all weekly Entry Periods to receive the prize listed below. If a winner declines, we will draw again at random for the next winner.  A user will only be able to win once overall. If they are drawn multiple times, another user will be drawn at random.  Individuals will be contacted before the announcement with the opportunity to claim or deny the prize.  Once all of the winners have been notified, we will post in the News & Announcements of each community with the list of winners.   Each winner will receive one (1) Pass to the Power Platform Conference in Las Vegas, Sep. 18-20, 2024 ($1800 value). NOTE: Prize is for conference attendance only and any other costs such as airfare, lodging, transportation, and food are the sole responsibility of the winner. Tickets are not transferable to any other party or to next year’s event.   ** PLEASE SEE THE ATTACHED RULES for this CHALLENGE**   Week 1 Results: Congratulations to the Week 1 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Community MembersNumber of SolutionsSuper UsersNumber of Solutions @anandm08  23 @WarrenBelz  31 @DBO_DV  10 @Amik  19 AmínAA 6 @mmbr1606  12 @rzuber  4 @happyume  7 @Giraldoj  3@ANB 6 (tie)   @SpongYe  6 (tie)     Week 2 Results: Congratulations to the Week 2 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Community MembersSolutionsSuper UsersSolutions @anandm08  10@WarrenBelz 25 @DBO_DV  6@mmbr1606 14 @AmínAA 4 @Amik  12 @royg  3 @ANB  10 @AllanDeCastro  2 @SunilPashikanti  5 @Michaelfp  2 @FLMike  5 @eduardo_izzo  2   Meekou 2   @rzuber  2   @Velegandla  2     @PowerPlatform-P  2   @Micaiah  2     Week 3 Results: Congratulations to the Week 3 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge.   Week 3:Community MembersSolutionsSuper UsersSolutionsPower Apps anandm0861WarrenBelz86DBO_DV25Amik66Michaelfp13mmbr160647Giraldoj13FLMike31AmínAA13SpongYe27     Week 4 Results: Congratulations to the Week 4 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge.   Week 4:Community MembersSolutionsSuper UsersSolutionsPower Apps DBO-DV21WarranBelz26Giraldoj7mmbr160618Muzammmil_0695067Amik14samfawzi_acml6FLMike12tzuber6ANB8   SunilPashikanti8

Check Out | 2024 Release Wave 2 Plans for Microsoft Dynamics 365 and Microsoft Power Platform

On July 16, 2024, we published the 2024 release wave 2 plans for Microsoft Dynamics 365 and Microsoft Power Platform. These plans are a compilation of the new capabilities planned to be released between October 2024 to March 2025. This release introduces a wealth of new features designed to enhance customer understanding and improve overall user experience, showcasing our dedication to driving digital transformation for our customers and partners.    The upcoming wave is centered around utilizing advanced AI and Microsoft Copilot technologies to enhance user productivity and streamline operations across diverse business applications. These enhancements include intelligent automation, AI-powered insights, and immersive user experiences that are designed to break down barriers between data, insights, and individuals. Watch a summary of the release highlights.    Discover the latest features that empower organizations to operate more efficiently and adaptively. From AI-driven sales insights and customer service enhancements to predictive analytics in supply chain management and autonomous financial processes, the new capabilities enable businesses to proactively address challenges and capitalize on opportunities.    

Updates to Transitions in the Power Platform Communities

We're embarking on a journey to enhance your experience by transitioning to a new community platform. Our team has been diligently working to create a fresh community site, leveraging the very Dynamics 365 and Power Platform tools our community advocates for.  We started this journey with transitioning Copilot Studio forums and blogs in June. The move marks the beginning of a new chapter, and we're eager for you to be a part of it. The rest of the Power Platform product sites will be moving over this summer.   Stay tuned for more updates as we get closer to the launch. We can't wait to welcome you to our new community space, designed with you in mind. Let's connect, learn, and grow together.   Here's to new beginnings and endless possibilities!   If you have any questions, observations or concerns throughout this process please go to https://aka.ms/PPCommSupport.   To stay up to date on the latest details of this migration and other important Community updates subscribe to our News and Announcements forums: Copilot Studio, Power Apps, Power Automate, Power Pages

Top Solution Authors
Users online (2,848)