Trigger Onchange JS with Bulk Edit – Unsupported

As Simple as this, You have a JavaScript which copies one field from to another using onchange event in the form, then remember JavaScript are triggered only when the form is opened or is being opened.

But what if you want to edit multiple records at once using the OOB grids, your code will not work. The fix is an 4.0 solution.

I term this as unsupported customization as I found in SDK that this should not be updated, but again similar kind of post MSDN EMEA which guides you how to do it.

To explain more:
The BehaviorInBulkEditForm attribute must be set to one of the following values:

  • Enabled: The field is enabled and the OnChange code is executed.
  • Disabled: The field is disabled and the OnChangeCode is not executed.
  • EnabledButNoRender: The field is enabled, but the OnChange code is not executed.

This is what we need to do:

  1. Export the entity as a solution for which JavaScript needs to be enabled during Bulk Edit.
  2. Open the customization.xml
  3. Add BehaviorInBulkEditForm=”Enabled” to the event handlers where your function is called.1

This worked even after multiple export and import of entity. Both for CRM 2011 and CRM 2013

Thanks!!!

Whats New in MS CRM 2013

Must Read.

Manoj Chauhan

Got little time to analyze CRM 2013 after so many days and here i found some great features which i missed in my earlier experiences with customer. CRM 2013 introduce a decent interface now with an intuitive, less cluttered interface it finally removes pop-up CRM windows that were frustrating characteristic of  MS CRM 4.0 and CRM 2011.

Compared to CRM 2011 the new version includes high level features:

• A new horizontal menu bar that ease user navigation & frees up screen space replacing the CRM left menu and ribbon navigation
• Each CRM module is grouped together in main navigation header including recently viewed items
• Quickly create new CRM records –  A short form overlay appears enabling new records to be created without changing screen, or opening a new window!
• Associate images with CRM records including contacts and users
• Integrated Bing Maps that dynamically shows the map…

View original post 89 more words

Steps to Debug plug-in with profiler in CRM 2011

Steps to Debug plug-in with profiler in CRM 2011

Plug-in profiler is a very powerful debugging tool in CRM 2011. We can debug plug-ins with Plug-in profiler without connecting to CRM server or without remote debugging. By this, no need to re-deploy the plug-in to the Microsoft Dynamics CRM server until you have fixed the problem.

Below are the steps to debug the plug-in with profiler:

  1. Connect to CRM using plugin registration tool.
  2. Click on Install Profiler
  3. You will find a new node attached to registered plugins “Plugin Profiler”
  4. Select a plug-in step and click Profile to enable profiling
  5. Start your plugin from MSCRM i.e. if your plugin is on Create, perform Create operation.
  6. After the plug-in throws an exception and the Business Process Error dialog is displayed, click Download Log File and save this file. Alternately, if the plug-in does not throw an exception, click Stop Profiling.
  7. In the Plug-in Registration tool, click Debug
  8. In the Debug Existing Plug-in dialog box, provide the location of the previously saved log file.
  9. In Step #2, specify the location of the plug-in assembly
  10. Launch Visual Studio 2010 and attach the debugger to the PluginRegistration.exe process.
  11. Set a breakpoint in the plug-in code.
  12. Click Start Plug-in Execution in the Debug Existing Plug-in dialog box.
  13. After a slight delay, the plug-in will execute using the same execution context that was passed to it by the Microsoft Dynamics CRM server and the debugger will stop execution on the breakpoint that you previously set.
  14. Continue debugging the plug-in as you would normally do. Any traces that the plug-in outputs are shown in the Debug Existing Plug-in dialog box.

Note: The Plug-in Profiler is available in version 5.0.5 of the Microsoft Dynamics CRM SDK and later releases. Read more here on how to Analyze Plug-in Performance.