Skip to main content

Custom Connector Deployment

In continuation to my previous blog on custom connector. Here is the blog on how to deploy connector to a new environment.

To move custom connectors from one environment to another. We have to perform 3 different actions.

1.       Adding connectors to Solutions.

2.       Exporting solutions 

3.       Importing solutions in new environment.


Click here to visit Power Automate Portal. Login with admin user credentials.


        •    Click on the “Solutions” tab on the left panel. Please refer image below.



 


































 

Note: Custom connectors created outside solutions cannot be added to solutions at this time.

 

Adding a connector to a solution

To add Custom Connector to Solutions below steps are to be followed.


•       Click on New Solution on top ribbon. Enter necessary details like solution name, version and so on and click on “Create” button.

 



































•       You should be able to see the newly created solution on the top. You can click and open it.

•       Click on “New” on the top ribbon and select “others” from the sub menu and select “Custom Connector”.



 

















•       You will now be redirected to a new tab with Connector Designer page.

•       Create your desired connector and click on Update connector on top right corner.

•       Once the connector is created you can visit previous tab and click on the “Done” button in popup.



 












•       You should be seeing your newly created connector on top of the solutions window.

 

Exporting a Solution

•       You can now see all the solutions that are imported to earlier.

•       Click on the eclipse icon (…) besides your solution name and click on “Export”.

•       You can now see a new window with “Before you Export” title.

•       Click on “Publish” if you have made any changes in this flow.

•       Click on “Run” to check if any issues exist.

•       Click on “Next”.


 































•       You can now see “Export this Solution” screen.

•       Specify your desired version number.

•       Select “Managed” radio button and click on export. You can see a .zip file downloading.

                 

Importing solutions to new environment

•       You already have the zip filed solution.

•       Click on “Import” from the top ribbon. 
 


 

•       You will now see a popup to choose the solution file that you downloaded earlier.

•       Click “Next” and then click on import.

You can now see the imported solution in the solutions gallery.

Labels

Labels:

Comments

Post a Comment

Popular posts from this blog

Business Data Connectivity

I came to a requirement wherein I was supposed to get data from an 3 rd party portal using API’s and then bring them to SharePoint server. The first approach that I finalized was just to make BDC solution that will get data from 3 rd party portal and will deploy it to SharePoint. How to Create BDC solution in SharePoint? I found below link that is having really great description about hot to create and deploy the BDC solution to SharePoint. http://www.c-sharpcorner.com/uploadfile/hung123/creating-business-data-connectivity-service-using-visual-studio-2010/ After creating an POC I came to know that BDC model cannot be deployed on Multi tenant farm. So what can be done next? After some amount of googling I came to know that we can create BDC solution using WCF services also. So I created a WCF service solution that acted as a wrapper that used to fetch data from the portal. We can them publish that service to IIS or Server and use the servic...
2 comments
Read more

Identity client runtime library (IDCRL) did not get a response from the login server.

Recently I was doing some testing with a background PowerShell and encountered a weird error. “Identity client runtime library (IDCRL) did not get a response from the login server”. The error that you might encounter while working with PowerShell. This error is very misleading when it comes to identifying what could go wrong. After doing quite a good amount of research below are the probable causes for the error. Invalid Credentials MFA (Multi-Factor Authentication) Manage security defaults. Solutions Invalid Credentials Check if your credentials are wrong. Especially if you are using variables. MFA (Multi-Factor Authentication) Check if MFA is enabled on the account which you are using. These only affect you badly if you are developing PowerShell for a background Job. Go to Microsoft 365 admin center Users -> Active users -> Select the user -> Manage multifactor authentication -> Select the user -> Disable multi-factor authentication. M...
2 comments
Read more

Copying Footers Between SharePoint Sites Using PnP PowerShell

Recently, I have been extensively working with SharePoint and the Patterns and Practices (PnP) PowerShell module. PnP has significantly simplified various tasks by providing easy-to-use command sets and thorough documentation. One particular task that PnP has made straightforward is copying a footer from one SharePoint site to another. This process can be achieved with just a few commands. Why Use PnP PowerShell? PnP PowerShell is a set of cmdlets designed to work with SharePoint Online and SharePoint on-premises. It simplifies the management and automation of common tasks and provides commands for nearly every aspect of SharePoint administration. The PnP module is especially useful for tasks that would otherwise require complex scripting or manual intervention. Copying a Footer with PnP PowerShell To copy a footer from one SharePoint site to another, follow these steps. This process involves exporting the footer template from the source site in XML format and...
Post a Comment
Read more