-
Notifications
You must be signed in to change notification settings - Fork 16
DynamicsCrm.DevKit.Config.json
DynamicsCrm.DevKit.Config.json is a VSIX configuration file stored in the Visual Studio solution root. It is separate from the connection file DynamicsCrm.DevKit.json and the CLI profile file DynamicsCrm.DevKit.Cli.json.
The VSIX uses this file for local solution features:
- Web resource mappings: a local file path mapped to a Dataverse web resource.
- Report mappings: a local
.rdlfile mapped to an existing Dataverse report by theDynamicsCrm.DevKit.2019lite VSIX. - Custom T4 templates: user-edited template bodies used by item-template customization dialogs.
{
"WebResources": [
{
"File": "src\\entities\\account.ts",
"WebResource": "new_/entities/account.js",
"WebResourceId": "00000000-0000-0000-0000-000000000000",
"IsManaged": false,
"SolutionUniqueName": "devkit"
}
],
"Reports": [
{
"File": "reports\\Top10Account.rdl",
"ReportId": "00000000-0000-0000-0000-000000000000",
"ReportName": "Top10Account",
"ReportFileName": "Top10Account.rdl",
"LanguageCode": 1033,
"Language": "English",
"IsManaged": false
}
],
"CustomTemplates": [
{
"Type": "Plugin",
"Title": "Default - Plugin",
"Body": "<custom t4 body>",
"IsDefault": true
}
]
}WebResources is updated by VSIX commands such as deploy web resource, deploy new web resource, deploy TypeScript release, and deploy new TypeScript release.
| Field | Description |
|---|---|
File |
Local file path selected in Visual Studio. |
WebResource |
Dataverse web resource unique name, for example new_/js/account.js. |
WebResourceId |
Dataverse web resource ID cached after lookup or creation. |
IsManaged |
Whether the selected Dataverse web resource is managed. |
SolutionUniqueName |
Solution unique name used when creating or adding the web resource. |
Once a mapping exists, DevKit can deploy the same local file again without asking the user to select the Dataverse web resource every time.
Reports is updated by the separate DynamicsCrm.DevKit.2019 lite VSIX when the Upload Dynamics 365 Report command maps a local .rdl file to an existing Dataverse report. This VSIX is distributed through GitHub Releases, not Visual Studio Marketplace.
| Field | Description |
|---|---|
File |
Local .rdl file selected in Visual Studio. |
ReportId |
Existing Dataverse report ID. |
ReportName |
Dataverse report display name. |
ReportFileName |
Dataverse report filename. |
LanguageCode |
Dataverse report language code. |
Language |
Dataverse report language label. |
IsManaged |
Whether the selected Dataverse report is managed. |
Within one Visual Studio session, the lite VSIX caches the selected mapping after the first confirmation. The next upload of the same .rdl deploys directly.
CustomTemplates is updated by the T4 customization UI used by item templates.
| Field | Description |
|---|---|
Type |
Item type, such as Plugin, Workflow, CustomApi, CustomAction, DataProvider, LateBound, JsForm, or TsForm. |
Title |
Template display name in the customization dialog. |
Body |
Saved T4 template body. |
IsDefault |
Whether this custom template should be selected by default for the item type. |
Default template names are reserved by the VSIX and cannot be duplicated by a custom template title.
| File | Purpose |
|---|---|
DynamicsCrm.DevKit.json |
Saved Dataverse connections. |
DynamicsCrm.DevKit.Cli.json |
CLI command profiles. |
DynamicsCrm.DevKit.Config.json |
VSIX web resource mappings, report mappings, and custom T4 templates. |
Related pages: