Advice on custom connector source code organization

Hi BenLambert,

Thank you for reaching out to the Microsoft fabric community forum. I have identified several alternative workarounds that may assist in resolving the thread.

As of now, Microsoft does not officially support importing shared .pqm modules from outside a single connector folder in the Power Query SDK.

You're on the right path by aiming to organize multiple Power Query custom connectors in a single repository with shared code. This approach is beneficial, especially when managing multiple connectors with similar functionalities.

Currently, the Power Query SDK for Visual Studio Code does not officially support referencing shared .pqm files from outside a single connector's project folder. Each connector is intended to be self-contained, as noted in the SDK documentation:

However, many developers have worked around this limitation by:

• Using symbolic links to include a shared Shared/ folder inside each connector directory.
• Writing simple build scripts that copy shared .pqm modules into each connector folder before building.

For building all connectors without manually opening each one in VS Code, consider using a PowerShell or shell script to iterate through each connector folder and invoke dotnet build. This can significantly streamline your workflow.

Additionally, you can configure a .code-workspace file to open all connector folders in one VS Code session, making development smoother.

Kinly refers to the below following documentation links for better understanding:
Power Query SDK Overview - Power Query | Microsoft Learn

If this post helps, then please give us ‘Kudos’ and consider Accept it as a solution to help the other members find it more quickly.

Thank you for using the Microsoft Community Forum.