PowerWebResource-Manager

Dynamics-For-Dev makes developing for Dynamics easier without leaving your coding environment.

Features

• Add new webresources to CRM
• Update existing web resources in CRM
• All webresource types are supported
• Use the Azure Authentication to connect to Dynamics Cusetomer Engagement (CRM)

Requirements

To connect to dynamics you need to sign in to azure with the Azure Account (identifier: ms-vscode.azure-account) extension. It should have been installed with this extension.

Also you need to have installed the Azure CLI tools from the official Microsoft documentation.

To check just search for Azure: Sign In in your Command Palette and sign in.

I recommend to use the command az login --allow-no-subscription in the terminal to log in. If the wrong browser window/profile opens for you just copy the url to the correct browser.

Use it

First you need to create a dynamicsConfig.json file. For this you just right click in your Visual Studio workspace explorer and select the new menu point "Add new dynamicsConfig.json".

Then you need to configure the json so you can upload the webresource. The target is that you only need to do this once.

After that:

You can call the upload command via the command palette in vs code. Search for "Dynamics-For-Dev: Upload WebResource" and follow the instructions. Alternatively you can right click a supported file (See Supported Files) and use the "Upload to Dynamics" command in the context menu.

To downlaod web resources from dynamics you can right click on your folder and choose "" and then follow the instructions.

NamingConvention

WebResourceFolder: The folder(s) in which your webresources are located. Use paths from the source workspace folder. No need to add the last "/".
Prefix: The prefix that will be added to your webresource when you upload it. You can use more than one but you need to select the correct one each time.

OrgInfo

CrmUrl: your environments url. Don't use the "/" at the end.
ApiVersion: The api version in your dynamics. This is 9.1 by default.

Solutions

This is an array of the uniquenames for your solutions.
You will be prompted to choose one of the solution to export. Exporting multiple solutions is not supported at the moment.
If you do not include this option in your json the extension will get every unmanaged solution in your system for you to select.

Sample

{
    "NamingConvention" : {
        "WebResourceFolder" : [ "/JsFoler1/path", "/Jsfolder2/path" ],
        "Prefix" : [ "new_/CustomJsFolder/", "new_" ]
    },
    "OrgInfo" : {
        "CrmUrl" : "https://yourorganization.yourregion.dynamics.com",
        "ApiVersion" : "9.1"
    },
    "UploadOptions" : {
        "AddExistingToSolution" : false,
        "TryToResolveFilePath" : false
    },
    "Solutions" : [ "MyCustomizationSolution", "MyPluginSolution" ]
}

UploadOptions

AddExistingToSolution: if you set this to true, it will ask you if you want to add the webresource to a solution even if it already exists. Otherwise it will just ask you if you create a new one.

TryToResolveFilePath: if set to true, it will try to automatically detect the correct path option of your file you want to upload. Only set this to true if you are sure it can be matched. It's still a bit experimental.

Supported files

• Webpage (.html)
• Style Sheet (.css)
• Script (.js)
• Data (.xml)
• PNG format (.png)
• JPG format (jpg, .jpeg)
• GIF format (.gif)
• Silverlight (.xap)
• Style Sheet (.xsl)
• ICO format (.ico)
• Vector format (.svg)
• String (.resx)

These are files supported by Dynamics. You can upload other file types (unknown too). But there is no guarantee that the uplaod will be successful.

Known Issues

You need to install Azure CLI in case you haven't. You need to restart after the installation.

If there is a authentication issue I recommend you to use az login --allow-no-subscription in the terminal to log you in. If the wrong browser window/profile opens for you just copy the url to the correct browser.

Errorhandling isn't aways giving feedback to the user. Will be corrected. If you experience an error please create an issue on the github page or message the author.

Release Notes

0.7.10 - Fixed vulnerability of package and error when retrieving webresources from dynamics

Fixed an error while retrieving webresources from dynamics if results would be empty/undefined npm package vulnerability fixed and updated.

0.7.9 - Fixed vulnerability of nanoid package and uploadoptions for all file types

npm package vulnerability fixed and updated.

0.7.8 - Fixed vulnerability of nanoid package and uploadoptions for all file types

npm package vulnerability fixed and updated.

0.7.7 - Fixed vulnerability of nanoid package and uploadoptions for all file types

You now can upload every file to dynamics if you want to. Updated npm packages to fix vulnerability of nanoid package.

0.7.6 - New option to resolve filepath automatically when

Added an option in the dynamicsConfig json to enable automatic path resolving if you use multiple paths Bugfix if you select an empty prefix it would add the "new_" prefix itself and would create a new file

0.7.5 - Fixed vulnerability of follow-redirect package

Updated npm packages to fix vulnerability of follow-redirect package.

0.7.4 - New Progress Indicator

Changed the progress notification window to show the progress.

Extension now opens dynamicsConfig.json file when it was created.

0.7.3 - General cleanup and global error handling

Added global error handling so you should always get a message in case an exception occurs.

0.7.2 - Fixed file path compatibility with Windows

Added a fix in which the extension couldn't use the file paths of Windows

0.7.0 - Added Export Solution functionality

Added context menu to export dynamics solution

0.6.2

Updated version for the marketplace

0.6.1

Marketplace infos added

0.6.0

Downloading WebResources now possible by right clicking a folder in your project

0.5.0

Initial release. Uploading WebResource to Dynamics now possible