Recommended approach for Custom connectors ALM

[Shidin]

Hi, 

Wanted to know what would be the "best practice" when working with Custom connectors. 

Our preference is to publish the custom connectors via API-M (since all APIs are managed by a seperate team). 

But once the custom connector is in Dev, how do we take it to QA or PROD?

We can include the custom connector in a solution. But we would have to update the API end-point in QA and PROD post-deployment. 

Wondering if that would cause any additional solution layers.

Any and all advice welcome! 🙂

TIA! 

[Syndicate_Admin · Accepted solution]

Hello,

What I usually do is put the custom connector in a separate solution and leverage an environment variable for the end point.

Best regards,

Alaa

[michelle-tc]

When putting it inside a solution, I am unable to share it with other developers on my team. How do you get around this issue or does only one developer have access to your custom connector?

[Syndicate_Admin]

The workaround to share the custom connector in solutions is to share it's Dataverse row (see video below).

In my tests, the maker needed System Customizer permission to create new connections for the custom connector (inside a new solution, in a new environment).

Sharing Custom Connectors In Solutions - Power CAT Live (youtube)