Unsigned / evaluation install¶
Fastest path to try the connector — tells Power BI Desktop to load any custom connector in the folder, signed or not. Use only for short evaluations on a disposable workstation.
Security implication
This setting relaxes the global trust check for every custom connector in your Custom Connectors folder — not just this one. For anything beyond a quick smoke test, follow the Self-signed cert install instead — same outcome, no weakened security posture.
1. Grab the .mez or .pqx¶
From the latest GitHub Release download OpenEHR.pqx. (If you built locally you may have a .mez instead — same shape.)
2. Drop the file into place¶
$dest = "$env:USERPROFILE\Documents\Power BI Desktop\Custom Connectors"
New-Item -ItemType Directory -Force -Path $dest | Out-Null
Copy-Item .\OpenEHR.pqx -Destination $dest -Force
3. Relax the data-extensions check¶
File → Options → Security → Data Extensions → "(Not recommended) Allow any extension to load without validation or warning"
flowchart LR
A[Power BI Desktop] --> B{Data Extensions<br/>setting}
B -->|Recommended| C[Only signed +<br/>trusted publishers<br/>load]
B -->|Not recommended<br/>evaluation only| D[Anything in<br/>Custom Connectors<br/>loads]
C --> E[OpenEHR.pqx loads<br/>only after cert import]
D --> F[OpenEHR.pqx loads<br/>immediately — but so<br/>does every other .mez]4. Restart and connect¶
- Fully quit and relaunch Power BI Desktop.
- Get Data → Other → openEHR (Beta).
- Enter the CDR base URL and credentials.
Limitations¶
- Does not work on the gateway. The on-premises gateway always requires signed connectors with trusted-publisher certs. See Gateway admin install.
- Does not survive Desktop reinstall. The setting is per-installation.
- SmartScreen may still flag the file on first open. Choose Run anyway.
When you're ready to move off this mode¶
Follow Self-signed cert install — import the publisher cert once, flip the Data Extensions setting back to Recommended, done.