• Home
  • About Us
  • Contact Us
  • Privacy Policy
  • Special Offers
Business Intelligence Info
  • Business Intelligence
    • BI News and Info
    • Big Data
    • Mobile and Cloud
    • Self-Service BI
  • CRM
    • CRM News and Info
    • InfusionSoft
    • Microsoft Dynamics CRM
    • NetSuite
    • OnContact
    • Salesforce
    • Workbooks
  • Data Mining
    • Pentaho
    • Sisense
    • Tableau
    • TIBCO Spotfire
  • Data Warehousing
    • DWH News and Info
    • IBM DB2
    • Microsoft SQL Server
    • Oracle
    • Teradata
  • Predictive Analytics
    • FICO
    • KNIME
    • Mathematica
    • Matlab
    • Minitab
    • RapidMiner
    • Revolution
    • SAP
    • SAS/SPSS
  • Humor

Using Connection References with Power Automate and Common Data Service

November 14, 2020   Microsoft Dynamics CRM

If you have not heard of Connection References yet, they are definitely worth looking into. There are a lot of great blogs out there already, such as our blog introducing the feature, as well as our Docs information.

At a high-level, connection references are solution-aware components that contain a reference which associates the connector used and the flow it resides in. When importing a solution that contains a flow from one environment to the other, this prevents you from needed to open the flow and re-establish connections. In this case, we will focus on the Common Data Service(current environment) connection reference.

There a few important things I want to call out.

Connection references are specific to a user and connection when being automatically created or automatically used within a flow connection. Connections within a flow can be manually updated to use a connection reference from another user’s connection if they exist.

Manually, they can be created from the Power Apps maker portal. These are also specific to a user’s connection.

From within a solution, click New and select Connect Reference (preview)

7266.pastedimage1605200068356v1 Using Connection References with Power Automate and Common Data Service

You will give it a unique name and I recommend this be unique, since that is what currently displays in the views. You will also have to select a connector and an existing connection for that connector type. If it doesn’t exist, you must create it. (note: a connection for that connector must also exist for this user in the destination org)

2068.pastedimage1605200079989v2 Using Connection References with Power Automate and Common Data Service

That is pretty straight forward.

How is a connection reference automatically created? In this case, a user does not have an existing connection reference in an environment where they want to build a flow. If this user creates a flow in this environment using the Common Data Service (Current environment) trigger or action, a connection reference will automatically be created.

When it is created automatically, it will look like below, using a default name:

6862.pastedimage1605200092513v3 Using Connection References with Power Automate and Common Data Service

The only way you can currently find the schema name of this connection reference, is to click the ellipses from this view and click Edit. Then, you will see this as below:

1754.pastedimage1605200105370v4 Using Connection References with Power Automate and Common Data Service

Now, if there is more than one person creating flows that use Common Data Service (current environment) connectors in that same environment that also do not have an existing connection reference, the same thing will happen for that user.

This means, if the user does not already have a connection reference that they own for Common Data Service (current environment) and they create a new flow using a trigger or action for that connector, another connection reference will be created with the exact same name for this user.

6470.pastedimage1605200117254v5 Using Connection References with Power Automate and Common Data Service

However, the schema name is different.

4118.pastedimage1605200129809v6 Using Connection References with Power Automate and Common Data Service

If you extend this scenario to 10-15 people, or more, in an environment building flows, you will end up with multiple connection references that appear to be the same. This can become confusing very quick, especially during import of the solution.

If a user already has an existing connection reference in an environment, using Common Data Service (current environment) and they create a new flow, it will automatically set that connection reference to the connector in the flow and will not create a new connection reference.

As a best practice, and to prevent having multiple connection references using the same name and causing confusion, each user can create a connection reference manually with a preferred naming convention before creating any flows.

If you are already in this situation, users can change the display name of existing connection references or create a new connection reference with the preferred name and reassign this to the existing flows.

To update the connection reference once you have a new one created, open the flow in the originating org and update the connections to use the new connection reference. This will update the destination org when imported.

6011.pastedimage1605200144420v7 Using Connection References with Power Automate and Common Data Service

There is a known issue right now, if you create a new solution with a flow or add a flow to an existing solution the connection reference it is not added to the solution. It must be added manually. Be aware of this, especially if that connection reference doesn’t exist in the destination environment. It will fail to import. If you encounter this and have multiple connection references using the default name of Common Data Service (current environment), you will have to go find the schema name that aligns with the missing connection reference and add it to the solution in the originating environment.

While connection references are in preview, one connection reference can only be used within a maximum of 16 flows. If the same connection needs to be used in more than 16 flows, then create another connection reference with a connection to the same connector. 

What happens when you this limit? You will a message like this when trying to save the flow (click image to expand)

3630.pastedimage1605200162194v8 Using Connection References with Power Automate and Common Data Service

What happens when User A creates a solution with a flow in one environment, using a connection and connection reference of User A, but User B imports this solution to the destination environment where User A does not have an existing connection.

User B, when importing the solution, will have the option to select their existing connection to tie to the connection reference or create a new connection. They could select below

0268.pastedimage1605200174487v9 Using Connection References with Power Automate and Common Data Service

or click + New Connection

8176.pastedimage1605200186946v10 Using Connection References with Power Automate and Common Data Service

Otherwise, User A would need to sign-in to the flow portal for the destination environment and create a connection. This would allow the user importing the solution to select the correct connection for the connection reference.

2781.pastedimage1605200197155v11 Using Connection References with Power Automate and Common Data Service

Thanks for reading!

Aaron Richards

Sr. Customer Engineer

Dynamics 365 and Power Platform

Let’s block ads! (Why?)

Dynamics 365 Customer Engagement in the Field

Automate, Common, Connection, data, Power, References, service, using
  • Recent Posts

    • Ba’al comes to CPAC, Ted Cruz jokes about his Cancun trip
    • Optimizing data migration/integration with Power Platform
    • AI Weekly: Biden calls for $37 billion to address chip shortage
    • NOT WHAT THEY MEANT BY “BUILDING ON THE BACKS OF….”
    • Why Healthcare Needs New Data and Analytics Solutions Before the Next Pandemic
  • Categories

  • Archives

    • February 2021
    • January 2021
    • December 2020
    • November 2020
    • October 2020
    • September 2020
    • August 2020
    • July 2020
    • June 2020
    • May 2020
    • April 2020
    • March 2020
    • February 2020
    • January 2020
    • December 2019
    • November 2019
    • October 2019
    • September 2019
    • August 2019
    • July 2019
    • June 2019
    • May 2019
    • April 2019
    • March 2019
    • February 2019
    • January 2019
    • December 2018
    • November 2018
    • October 2018
    • September 2018
    • August 2018
    • July 2018
    • June 2018
    • May 2018
    • April 2018
    • March 2018
    • February 2018
    • January 2018
    • December 2017
    • November 2017
    • October 2017
    • September 2017
    • August 2017
    • July 2017
    • June 2017
    • May 2017
    • April 2017
    • March 2017
    • February 2017
    • January 2017
    • December 2016
    • November 2016
    • October 2016
    • September 2016
    • August 2016
    • July 2016
    • June 2016
    • May 2016
    • April 2016
    • March 2016
    • February 2016
    • January 2016
    • December 2015
    • November 2015
    • October 2015
    • September 2015
    • August 2015
    • July 2015
    • June 2015
    • May 2015
    • April 2015
    • March 2015
    • February 2015
    • January 2015
    • December 2014
    • November 2014
© 2021 Business Intelligence Info
Power BI Training | G Com Solutions Limited