Skip to content

Latest commit

 

History

History
60 lines (41 loc) · 2.4 KB

sample-import-files-web-resources.md

File metadata and controls

60 lines (41 loc) · 2.4 KB
Raw
title description keywords ms.date ms.custom ms.topic applies_to ms.assetid author ms.author ms.reviewer ms.suite ms.tgt_pltfrm caps.latest.revision topic-status search.audienceType
Sample: Import files as web resources (Developer Guide for Dynamics 365 Customer Engagement (on-premises)) | MicrosoftDocs
The sample provides a simplified example of importing files as web resources.
10/31/2017
sample
Dynamics 365 Customer Engagement (on-premises)
0f9bca5b-b876-4f68-8e4e-e844da8598d6
JimDaly
jdaly
pehecke
19
Drafting
developer

Sample: Import files as web resources

When you develop a large number of files to use as Web resources you can save yourself the work of manually adding them through the application. Many Web resources can be developed and tested outside of Dynamics 365 for Customer Engagement and then imported.

This sample provides a simplified example of this process. For a more complex sample that provides a WPF application you can use to import Web resources, see the Sample: Web Resource Utility.

[!includecc-sample-note]

You can download the sample from here.

How to run this sample

[!includecc-how-to-run-samples]

What this sample does

This sample will show how to use the SolutionUniqueName optional parameter to associate a web resource with a specific solution when it is created.

How this sample works

In order to simulate the scenario described in What this sample does, the sample will do the following:

Setup

  1. Checks for the current version of the org.
  2. The CreateRequiredRecords class creates a publisher and a solution required for the sample when adding the web resources.

Demonstrate

  1. The XDocument method reads the descriptive data from the XML files.
  2. The WebResource is used to set the web resource properties.
  3. The CreateRequest method is used to add optional parameters.

Clean up

Display an option to delete the sample data that is created in Setup. The deletion is optional in case you want to examine the entities and data created by the sample. You can manually delete the records to achieve the same result.

[!INCLUDEfooter-include]