What is Secure Vs Unsecure configuration of plugin in Dynamics 365 CRM

While developing plugin for Microsoft Dynamics CRM, there are some scenarios where you required an input parameters or a configuration for the plugin execution which can be easily updated without having to re-compile or re-registering the plugin.

When you register a plugin step, there are fields where you can specify configuration parameters for the plugin execution.

In Microsoft Dynamics CRM there are two types of different configurations fields are available for plugin-

1. Unsecure configuration.

2. Secure configuration.

The main difference between these two settings is that, secure configuration is only viewable by CRM Administrators while the unsecure configuration is viewable by any CRM user.

Another major difference is- the unsecure configuration will automatically move between environments with your CRM solutions.

How to use the plugin step configuration:

While registering the new step in plugin you can provide the configuration data with the Secured or Unsecured fields as show in the below screenshot-

When you provide the configuration details in XML format in the constructor of your plugin class you will get the configuration value which you can use later in the execution method.

Comments

Microsoft Dynamics 365 CRM Troubleshooting Solution Import Errors

Remember when CRM life was so much simpler that solutions did not yet exist? If you had separate development and production environments and you wanted to move your customizations, you simply clicked Export Customizations and voila! It was done. Those were the days. Nostalgia Warning – in case you’ve forgotten, here’s a screenshot to jog your memory: With CRM 2011, the concept of solutions was introduced, giving us a new set of powers – by picking individual entities, workflows, etc., we now had the ability to group together and move only those customizations we wanted to include in our solution. The next great solutions advancement came with CRM 2016: we can now select specific components within each individual entity – so instead of moving the entire contact entity, for example, we have the option of moving only a certain view or field within the entity. And we can do this without having to hack the xml in the zip file. (By the way, if you want to learn more abou...

How to Filter SubGrid Lookup view in Dynamics 365 CRM

How to Filter SubGrid Lookup view in Dynamics 365 CRM. Please check the comments in the below code and do follow the steps accordingly and call the filterSubGrid() funtion on onload. var LastQuery = ""; function filterSubGrid() { debugger; setSubgridLookupFiltering(); } function AddLookupFilter(entity_type, customFilter) { var subgridLookup = Xrm.Page.getControl("lookup_Contacts_Participants"); subgridLookup.addCustomFilter(customFilter, entity_type); } function setSubgridLookupFiltering() { var subgridAddButtonId = "Contacts_Participants_addImageButton"; //Try to get the element from both the current and the parent document. var subgridAddButton = document.getElementById(subgridAddButtonId) || window.parent.document.getElementById(subgridAddButtonId); //This script may run before the subgrid has been fully loaded on the form. If this is the case, //delay and retry until the subgrid has been loaded. if (subg...

How to prevent record from saving in Dynamics CRM using Javascript

From time to time you might need to add some validation to the save event of an entity, this actually used to be an approach I would use on a regular basis but since the introduction of business rules have found myself doing this less and less. But still, knowing the ability is available is handy. When you define the onsave event function, you must tick the “Pass execution contact as first parameter” option. (See below) Having done that you can create an onSave function with code similar to the example I have shown below. Note forgetting the “(context)”, which will take the context parameter allowing you to prevent the save when needed. function onSave(context) { var saveEvent = context.getEventArgs(); if (Xrm.Page.getAttribute("telephone1").getValue() == null) { // *** Note: I am using an alert for testing a notification maybe better! alert("Put in a phone number!"); saveEvent.preventDefault(); } } Note: This simple example might be better achi...

Dynamics 365 CRM

Search This Blog