-
Notifications
You must be signed in to change notification settings - Fork 2
Troubleshooting
Start here when something doesn't work. The single most useful step:
Dataverse PowerTools: Show Log — opens the extension's output channel, where every connection, build, and deploy step is logged. Most fixes start with reading it.
| Symptom | Fix |
|---|---|
| Status bar shows Dataverse Not Connected | Run Refresh Dataverse Connection. If it persists, Update Dataverse Authentication and re-enter details. |
Error refreshing authorization token |
The token expired or the secret changed — Refresh Dataverse Connection, or re-run Update Dataverse Authentication. |
| Environment list is empty (service principal) | The app isn't an Application User in that environment; add it, or type the URL manually when prompted. |
| Credentials seem lost between sessions | Reconnect with Refresh Dataverse Connection. Secrets live in VS Code secret storage per machine — a fresh clone always needs to authenticate once. |
More: Connecting & Authentication.
| Symptom | Fix |
|---|---|
| A row is ✗ in the System Requirements card | Install the missing tool via its Download link (Getting Started), then Recheck Requirements. |
Commands that call dotnet/pac do nothing |
Confirm .NET SDK and pac are installed and on PATH; reopen the terminal/VS Code after installing so PATH refreshes. |
npm ERESOLVE while creating a Web Resources project |
Fixed in current versions (TypeScript pinned). Update the extension; if you still hit it, delete node_modules and re-run Restore Dependencies. |
The extension runs on Windows, macOS, and Linux — including web resource typings (a bundled
cross-platform XrmDefinitelyTyped via dotnet) and, since 1.0.7, capturing a plug-in profile
(Profile next run), which no longer uses a .NET Framework tool.
What still needs .NET Framework is running the replay test — your plug-in test project targets
net471, so dotnet test needs the Framework test host (on Linux it builds, then aborts with
"Could not find 'mono' host"). Use Windows, or install mono. Everything up to that point —
capture, Download a run, Generate Replay Test, trace logs — is native on every OS. See
Profiling a Plug-in Run.
- Solutions → Solutions › Troubleshooting
- Web Resources → Web Resources › Troubleshooting
- Plugins → Plugins › Troubleshooting
- Portals → Portals › Troubleshooting
Open an issue on the GitHub repository with the relevant output from Show Log (redact any secrets first).