web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

Check out the Community Spotlight Video Series
News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Microsoft Dynamics CRM (Archived) / plugin registration to...
Microsoft Dynamics CRM (Archived)

plugin registration tool - registration option stuck as isolated?

(0) ShareShare
ReportReport
Posted on by Community Member

Hello, I'm currently in the process of registering a new plugin. All of my previous plugins were registered normally. However, when I select the latest plugins dll through the Update button in the PRT, the selected plugins dll has " - Isolatable" after each plugin in the assembly that was selected. These are the default settings in the "Update Assembly" dialog:

Isolation Mode=None
Location=Database

All of the plugins in my previous plugins.dll were registered without " - Isolatable" at the end. However, for some reason, they all now display " - Isolatable" in the "Update Assembly" dialog, although the plugins that were already registered do not display this in the normal PRT "Registered Plugins" view. Any idea why I might be seeing this behavior? I don't want to register the new plugin as Isolated or update existing plugins to be Isolated.

*This post is locked for comments

I have the same question (0)
  • Community Member Profile Picture
    Community Member on at

    Hi Guido, I haven't made any changes to the SDK or PRT in my environment.  Sounds like simply having a plugin with "Isolatable" in the name:

    * doesn't create additional limitations for the plugin

    * doesn't make security less restrictive for the plugin

    It really only means that the plugin has the *ability* to be registered in the sandbox for reduced functionality. I'm assuming that this is probably some sort of bit setting with *minimal* if any performance impact to support the overhead of supporting 2 different modes for the plugin.

    However, I could see someone arguing that they wouldn't want a plugin to be "isolatable" because it could potentially allow a deployment admin to improperly register the plugin in the Sandbox which could unknowingly impact/reduce the expected plugin functionality. So is there any possible way to specifically remove the "Isolatable" setting from a plugin?

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

News and Announcements

Check out the Community Spotlight Video Series

Quick Links

Season of Sharing Community Challenge Winners!

Congratulations to our community stars!

Women in Power Builds Momentum

Expanding mentorship, skilling, and AI innovation

Congratulations to the July Top 10 Community Leaders

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics CRM (Archived)

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans