Dynamics Community Forum Thread Details

Hello BK-17051419-0,

That's interesting that the Microsoft.Dynamics.OmnichannelBotExtension.Plugins.PostOperationAddBotSessionPlugin is running in your Dynamics 365 environment even though you don't utilize Omnichannel or bots. This suggests that the plugin might be registered due to the installation of a solution that includes components related to Omnichannel, even if you aren't actively using those features.

Here's how you can investigate and potentially disable this plugin:

1. Access the Plugin Registration Tool:

You'll need to use the Plugin Registration Tool to view and manage registered plugins and steps in your Dynamics 365 environment. This tool is part of the Dynamics 365 SDK (Developer Toolkit).

If you have the SDK installed: Navigate to the Tools\PluginRegistration folder within your SDK installation directory and run PluginRegistration.exe.

If you don't have the SDK installed: You can download it from the Microsoft Download Center. Search for "Microsoft Dynamics 365 SDK." Once downloaded, extract the contents and find the PluginRegistration.exe in the Tools\PluginRegistration folder.

2. Connect to Your Dynamics 365 Environment:

Open the Plugin Registration Tool.

Click Create new connection.

Choose how you want to connect (typically using a connection string or providing credentials).

Enter your Dynamics 365 instance details and click Login.

3. Locate the Plugin Assembly:

Once connected, you'll see a list of registered Plugin Assemblies.

Look for an assembly named something like "Microsoft.Dynamics.OmnichannelBotExtension.Plugins".

4. Find the Specific Plugin:

Expand the "Microsoft.Dynamics.OmnichannelBotExtension.Plugins" assembly.

You should see a list of the plugins within that assembly.

Locate the plugin named "Microsoft.Dynamics.OmnichannelBotExtension.Plugins.PostOperationAddBotSessionPlugin".

5. Examine the Plugin Steps (Execution Pipeline):

Expand the "Microsoft.Dynamics.OmnichannelBotExtension.Plugins.PostOperationAddBotSessionPlugin".

You will see a list of Steps (also known as SDK message processing steps) that define when and how this plugin executes. These steps specify the:
- Message: The Dynamics 365 operation that triggers the plugin (e.g., Create, Update).
- Primary Entity: The entity on which the operation is performed.
- Execution Stage: When the plugin executes in the pipeline (e.g., Pre-operation, Post-operation).
- Execution Order: The sequence in which plugins execute within a stage.
- Filtering Attributes: Specific attributes that, when changed, trigger the plugin (for Update messages).
- Deployment Mode: Server-side or Client-side.
- Execution Mode: Synchronous or Asynchronous.

6. Identify the Relevant Plugin Steps:

Review the list of steps associated with the PostOperationAddBotSessionPlugin. Look for steps that seem to be executing under conditions that are occurring in your environment, even though you don't use Omnichannel. For example, it might be registered on the Create of a specific entity that is used in other parts of your system.

7. Disable the Plugin Step(s):

Once you've identified the step(s) you want to prevent from running:
- Right-click on the specific Step.
- Select Unregister.
- Confirm that you want to unregister the step.

Important Considerations and Potential Reasons for its Execution:

Solution Dependencies: The OmnichannelBotExtension plugin might be part of a larger solution that you have installed for other reasons. Disabling it could potentially impact other functionalities if those functionalities have dependencies on this plugin (though this is less likely if you don't actively use Omnichannel features).

Accidental Registration: It's possible the plugin step was registered inadvertently during a customization or solution import.

Future Feature Preparation: In some cases, Microsoft solutions might include components that are not immediately active but are there in preparation for future features or integrations.

Best Practices:

Disable Steps, Not the Entire Plugin: It's generally better to disable specific plugin steps rather than the entire plugin assembly if other plugins in that assembly might be necessary.

Test Thoroughly in a Non-Production Environment: Before disabling any plugin steps in your production environment, perform the same actions in a sandbox or development environment to ensure it doesn't cause any unintended side effects on your existing processes.

Document Your Changes: Keep a record of any plugin steps you disable and the reason for doing so. This will be helpful for future troubleshooting or when reviewing your system configuration.

By using the Plugin Registration Tool, you should be able to pinpoint the specific execution context of the PostOperationAddBotSessionPlugin and disable the relevant steps to prevent it from running unnecessarily in your Dynamics 365 environment. Remember to proceed with caution and test your changes thoroughly.

If my answer was helpful, please click Like, and if it solved your problem, please mark it as verified to help other community members find more. If you have further questions, please feel free to contact me.

My response was crafted with AI assistance and tailored to provide detailed and actionable guidance for your Microsoft Dynamics 365 query.

Regards,

Daivat Vartak

Community site session details

Microsoft.Dynamics.OmnichannelBotExtension.Plugins.PostOperationAddBotSessionPlugin

Helpful resources

News and Announcements

Quick Links

Responsible AI policies

Andrés Arias – Community Spotlight

Congratulations to the August Top 10 Community Leaders!

Leaderboard > Customer experience | Sales, Customer Insights, CRM

Featured topics

Product updates