Skip to content

New Control

Jump to bottom
Danish Naglekar edited this page Oct 7, 2019 · 1 revision

From Blank

  1. Initialize PCF project: Here you define your Namespace and Control Name. Both should not contain any space in them.
  2. Develop custom control
    • Open Project Directory: It opens the custom control directory in Windows Explorer
    • Open in VS Code: It opens the folder in Visual Studio Code
  3. Build PCF project: Runs the build command. If the build is successful, plugin will show the result on the top right corner near Quick Action and the built-in command prompt will show the result of the execution.
  4. Test custom control: This will run the command outside of the plugin because it needs user action to close the process. With this execution you can test your custom control in two ways
    • Test Project: A disconnected way of testing, if any changes are made in the code, you will have to close the testing window, build the code and run the test again.
    • Test project with Watch: A better, connected way of testing. With this if any changes are made to the code, CLI is able to detect those changes rebuild the control and reloads the control in the browser. This saves lot of time going back-and-forth.
  5. Initialize CDS project: Define you Solution name, Publisher name and prefix. Currently, the plugin does not allow spaces in the names.
  6. Deploy to D365 CE: Once the custom control is ready, deploy the control directly in you D365 CE or CDS environment using XrmToolbox connection.

From Template

Plugin will present list of custom controls build by the community. Here you can search either by the Name (or part) of the control or by the author. This dialog provides you the description and link to actual control in PCF Gallery. It also presents you with a “Download” button which when clicked downloads the repo from GitHub into your working directory and tries to load the control details on the “Builder” tab. Once downloaded, you can edit the control as per your liking or take a peak at the code.

Clone this wiki locally