1. One place for all extensions for Visual Studio, Azure DevOps Services, Azure DevOps Server and Visual Studio Code. Discover and install extensions and subscriptions to create the dev environment you need.
  2. Plugin supports two renders: Local and PlantUMLServer. Local is the default and traditional way. If you care more about export speed, you should try PlantUMLServer.
  1. Visual Studio Plugin For Qt
  2. Visual Studio Plugins For React
  3. Visual Studio Plugin Download
  4. Visual Studio Plugin Folder

View Pull Requests in Visual Studio. View all of the Pull Requests for your project in the GitHub pane, and sort and filter them by Open/Closed state, Assignee and Author. Open the GitHub pane by typing GitHub into Visual Studio Quick Launch (Ctrl+Q).

-->

Note

Unsure about entity vs. table? See Developers: Understand terminology in Microsoft Dataverse.

This tutorial is the first in a series that will show you how to work with plug-ins. This tutorial is a pre-requisite for the following tutorials:

For detailed explanation of supporting concepts and technical details see:

Goal

Create an asynchronous plug-in registered on the Create message of the account table. The plug-in will create a task activity that will remind the creator of the account to follow up one week later.

Note

This goal can be easily achieved using a workflow without writing code. We are using this simple example so that we can focus on the process of creating and deploying a plug-in.

Prerequisites

  • Administrator level access to a Microsoft Dataverse environment
  • A model-driven app that includes the account and task tables.
    • If you don't have a model-driven app that includes these, see Build your first model-driven app from scratch for steps to make one in just a few minutes.
  • Visual Studio 2017 (or later version)
  • Knowledge of the Visual C# programming language
  • Download the Plug-in Registration tool.
    • Information about downloading the Plug-in registration tool is at : Download tools from NuGet. That topic includes instructions to use a PowerShell script to download the latest tools from NuGet.

Create a plug-in project

You need to use Visual Studio to write a plug-in. Use these steps to write a basic plug-in. Alternately, you can find the complete plug-in solution files here: Sample: Create a basic plug-in.

Create a Visual Studio project for the plug-in

  1. Open Visual Studio and open a new Class Library (.NET Framework) project using .NET Framework 4.6.2

    The name used for the project will be the name of the assembly. This tutorial uses the name BasicPlugin.

  2. In Solution Explorer, right-click the project and select Manage NuGet Packages… from the context menu.

  3. Select Browse and search for Microsoft.CrmSdk.CoreAssemblies and install the latest version.

  4. You must select I Accept in the License Acceptance dialog.

    Note

    Adding the Microsoft.CrmSdk.CoreAssemblies NuGet package will include these assemblies in the build folder for your assembly, but you will not upload these assemblies with the assembly that includes your logic. These assemblies are already present in the sandbox runtime.

    Do not include any other NuGet packages or assemblies to the build folder of your project. You cannot include these assemblies when you register the assembly with your logic. You cannot assume that the assemblies other than those included in the Microsoft.CrmSdk.CoreAssemblies NuGet package will be present on the server and compatible with your code.

  5. In Solution Explorer, right-click the Class1.cs file and choose Rename in the context menu.

  6. Rename the Class1.cs file to FollowupPlugin.cs.

  7. When prompted, allow Visual Studio to re-name the class to match the file name.

Edit the class file to enable a plug-in

  1. Add the following using statements to the top of the FollowupPlugin.cs file:

  2. Implement the IPlugin interface by editing the class.

    Note

    If you just type : IPlugin after the class name, Visual Studio will auto-suggest implementing a stub for the Execute Method.

  3. Replace the contents of the Execute method with the following code:

About the code

  • The ITracingService enables writing to the tracing log. You can see an example in the final catch block. More information: Use tracing
  • The IPluginExecutionContext provides access to the context for the event that executed the plugin. More information: Understand the execution context.
  • The code verifies that the context InputParameters includes the expected parameters for the CreateRequest that this plug-in will be registered for. If the Target property is present, the Entity that was passed to the request will be available.
  • The IOrganizationServiceFactory interface provides access to a service variable that implements the IOrganizationService interface which provides the methods you will use to interact with the service to create the task.

Add business logic

The plug-in will create a task activity that will remind the creator of the account to follow up one week later.

Add the following code to the try block. Replace the comment: // Plug-in business logic goes here. with the following:

About the code

  • This code uses the late-bound style to create a task and associate it with the account being created. More information: Create tables using the Organization service
  • Early bound classes can be used, but this requires generating the classes for the tables and including the file defining those classes with the assembly project. This is mostly a personal preference, so those steps have been left out of this tutorial for brevity. More information: Late-bound and early-bound programming using the Organization service
  • The Id of the account being created is found in the context OutputParameters and set as the regardingobjectid lookup column for the task.

Build plug-in

In Visual Studio, press F6 to build the assembly. Verify that it compiles without error.

Sign the plug-in

  1. In Solution Explorer, right click the BasicPlugin project and in the context menu select Properties.

  2. In the project properties, select the Signing tab and select the Sign the assembly checkbox.

  3. In the Choose a strong name key file: dropdown, select <New…>.

  4. In the Create Strong Name Keydialog, enter a key file name and deselect the Protect my key file with a password checkbox.

  5. Click OK to close the Create Strong Name Key dialog.

  6. In the project properties Build tab, verify that the Configuration is set to Debug.

  7. Press F6 to build the plug-in again.

  8. Using windows explorer, find the built plug-in at: binDebugBasicPlugin.dll.

Note

Build the assembly using Debug configuration because you will use the Plug-in Profiler to debug it in a later tutorial. Before you include a plug-in with your solution, you should build it using the release configuration.

Register plug-in

Visual Studio Plugin For Qt

To register a plug-in, you will need the Plug-in Registration tool

Connect using the Plug-in Registration tool

  1. After you have downloaded the Plug-in registration tool, click the PluginRegistration.exe to open it.

  2. Click Create new Connection to connect to your instance.

  3. Make sure Office 365 is selected. If you are connecting using a Microsoft account other than one you are currently using, click Show Advanced.

  4. Enter your credentials and click Login.

  5. If your Microsoft Account provides access to multiple environments, you will need to choose an environment.

  6. After you are connected, you will see any existing registered plug-ins & custom workflow activities

Register your assembly

  1. In the Register drop-down, select New Assembly.

  2. In the Register New Assembly dialog, select the ellipses () button and browse to the assembly you built in the previous step.

  3. For Microsoft 365 users, verify that the isolation mode is set to sandbox and the location to store the assembly is Database.

    Note

    Other options for isolation mode and location apply to on-premises Dynamics 365 deployments. For the location, you can specify the D365 server's database, the server's local storage (disk), or the server's Global Assembly Cache. For more information see Plug-in storage.

  4. Click Register Selected Plug-ins.

  5. You will see a Registered Plug-ins confirmation dialog.

  6. Click OK to close the dialog and close the Register New Assembly dialog.

  7. You should now see the (Assembly) BasicPlugin assembly which you can expand to view the (Plugin) BasicPlugin.FollowUpPlugin plugin.

Register a new step

  1. Right-click the (Plugin) BasicPlugin.FollowUpPlugin and select Register New Step.

  2. In the Register New Step dialog, set the following fields:

    SettingValue
    MessageCreate
    Primary Entityaccount
    Event Pipeline Stage of ExecutionPostOperation
    Execution ModeAsynchronous
  3. Click Register New Step to complete the registration and close the Register New Step dialog.

  4. You can now see the registered step.

Note

At this point the assembly and steps are part of the system Default Solution. When creating a production plug-in, you would add them to the unmanaged solution that you will distribute. These steps are not included in this tutorial. See Add your assembly to a solution and Add step to solution for more information.

Test plug-in

  1. Open a model-driven app and create an account table.

  2. Within a short time, open the account and you can verify the creation of the task.

What if the task wasn't created?

Because this is an asynchronous plug-in, the operation to create the task occurs after the account is created. Usually, this will happen immediately, but if it doesn't you may still be able to view the system job in the queue waiting to be applied. This step registration used the Delete AsyncOperation if StatusCode = Successful option which is a best practice. This means as soon as the system job completes successfully, you will not be able to view the system job data unless you re-register the plug-in with the Delete AsyncOperation if StatusCode = Successful option unselected.

However, if there was an error, you can view the system job to see the error message.

View System jobs

Use the Dynamics 365 --custom app to view system jobs.

  1. In your model-driven app, navigate to the app

  2. In the Dynamics 365 --custom app, navigate to Settings > System > System Jobs.

  3. When viewing system jobs, you can filter by Table (Entity). Select Account.

  4. If the job failed, you should see a record with the name BasicPlugin.FollowupPlugin: Create of account

  5. If you open the system job, you can expand the Details section to view the information written to the trace and details about the error.

Query System jobs

You can use the following Web API query to return failed system jobs for asynchronous plug-ins.

Visual Studio Plugins For React

More information: Query data using the Web API

Or use the following FetchXml:

More information: Use FetchXML with FetchExpression

View trace logs

The sample code wrote a message to the trace log. The steps below describe how to view the logs.

By default, plug-in trace logs are not enabled.

Tip

IF you prefer to change this setting in code:This setting is in the Organization table PluginTraceLogSetting column.

The valid values are:

Visual
ValueLabel
0Off
1Exception
2All

Visual Studio Plugin Download

Use the following steps to enable them in a model-driven app.

  1. Open the Dynamics 365 - custom app.

  2. Navigate to Settings > System > Administration.

  3. In Administration, select System Settings.

  4. In the System Settings dialog, in the customization tab, set Enable logging to plug-in trace log to All.

    Note

    You should disable logging after you are finished testing your plug-in, or at least set it to Exception rather than All.

  5. Click OK to close the System Settings dialog.

  6. Repeat the steps to test your plug-in by creating a new account.

  7. In the Dynamics 365 -- custom app, navigate to Settings > Customization > Plug-In Trace Log.

  8. You should find that a new plug-in trace Log record has been created.

  9. If you open the record you might expect that it would include the information you set in your trace, but it does not. It only verifies that the trace occurred.

  10. To see the details, it is easier to query this data using the Web API in your browser using the following query with the plugintracelog EntityType, using the typename property to filter results in the messageblock property based on the name of the plug-in class:

    GET <your org uri>/api/data/v9.0/plugintracelogs?$select=messageblock&$filter=typename eq 'BasicPlugin.FollowUpPlugin'

  11. You can expect to see the following returned with the Web API query:

Next steps

In this tutorial you have created a simple plug-in and registered it. Complete Tutorial: Debug a plug-in to learn how to debug this plug-in.

Visual Studio Plugin Folder

Note

Can you tell us about your documentation language preferences? Take a short survey.

The survey will take about seven minutes. No personal data is collected (privacy statement).