Getting Your Clash Sets in External Applications

Overview

ClashWise provides an editable Power BI Project with five report pages, a shared semantic model, relationships, measures, and ten paged reporting tables. Every table loads through the ClashWise Power Query connector and your ClashWise OAuth sign-in.

The installation page and downloads are public. A ClashWise sign-in is required only when the report connects to data. The report is read-only and sees the projects that account can access; membership changes apply on the next refresh.

Before you begin

The production connector is publicly distributed by ClashWise as ClashWise.mez. It is a self-distributed custom connector, not yet a built-in or Microsoft-certified connector.

1. Close Power BI Desktop.
2. Download ClashWise.mez from /integrations/power-bi. If Windows shows Unblock in the file's Properties dialog, select it.
3. Put it in [Documents]\Microsoft Power BI Desktop\Custom Connectors. Your effective Documents folder can be redirected by OneDrive, so use the Documents folder Windows opens for your account rather than assuming a fixed path.
4. In Power BI Desktop, open File → Options and settings → Options → Security. Under Data Extensions, allow uncertified extensions and select OK.
5. Restart Power BI Desktop, select Get Data, and confirm ClashWise is available.

Only install the connector downloaded from the public ClashWise integration page.

Set up the report

1. Open /integrations/power-bi and download the English report package.
2. Extract the package.
3. Open ClashWiseAnalytics.pbip in Power BI Desktop.
4. Select Refresh. When prompted, choose the ClashWise data source.
5. Power BI opens ClashWise OAuth in your browser. Sign in with your normal ClashWise account.
6. Review the read-only reporting permission and approve access.
7. Return to Power BI Desktop and allow all ten tables and five report pages to refresh.

There is no reporting password to create or paste. The production connector is fixed to the ClashWise production service and renews its OAuth session when needed.

Refresh in Power BI Desktop

Select Refresh to load the current data available to your organization membership. If your membership is removed or the authorization is revoked, the next refresh is denied. Data that Power BI already imported remains in the report until you remove or replace it.

Scheduled refresh before certification

Until Microsoft certifies and distributes the ClashWise connector, scheduled refresh in Power BI Service requires a Standard on-premises data gateway running the same custom connector.

1. Install the same ClashWise.mez downloaded from ClashWise in the gateway's configured custom connector folder, accessible to the gateway service account.
2. Restart the gateway and confirm that it loads the connector.
3. Publish the Power BI Project to your workspace.
4. Create the ClashWise gateway data source, complete OAuth sign-in, and bind the semantic model to it.
5. Run an on-demand refresh successfully before enabling a schedule.

Microsoft currently limits OAuth authentication for custom connectors through the gateway to gateway administrators. Your gateway team may therefore need to complete the data-source sign-in even though every active ClashWise organization member can use the Desktop connector.

Revoke access

Open Connected Apps at /my/connected-apps, find the Power BI authorization, and select Revoke. Revocation blocks future token renewal and refresh; it does not delete data already imported into Power BI.

Included data

• Projects and original clash sets
• Current clashes, permanent clash numbers, workflow state, priority, contact, and due dates
• Clash history and tags
• Matrices, rules, configured options, and configured colors
• Quantitative coordination-session outcomes
• Shared-insight metadata and usage counts

Notes, comments, attachments, viewpoints, passwords, member identities, and Wise-generated prose are excluded from the reporting feed.

Troubleshooting

• ClashWise is missing from Get Data: confirm ClashWise.mez is in the correct Custom Connectors folder, uncertified extensions are allowed, and Power BI Desktop was restarted.
• Sign-in is denied: confirm that your ClashWise account and organization membership are active and that you can open the relevant projects in ClashWise.
• Desktop works but Service refresh fails: confirm that the gateway uses the same connector version, can reach the ClashWise production service, and has a valid ClashWise OAuth data source bound to the semantic model.
• Access was revoked: refresh again and complete consent only if you intend to reconnect.

Legacy custom integrations

The older /export/* endpoints and profile-owned API keys remain available for existing custom integrations. They are a separate compatibility surface and are not used by the connector-backed Power BI templates.