Manipulation Library for CRM 2015


Manipulation Library had helped me lot with implementation of CRM 2011. But unfortunately the same CRM 2011 solution of Manipulation Library available on Codeplex here does not work with CRM 2015 as CRM 2015 requires assemblies to be developed with .Net Framework 4.5. Unfortunately, update for the solution on Codeplex is yet to come but a workaround is provided in discussions which is as below.

  1. Download and install Visual Studio 2013 (I used the free community versionhttp://www.visualstudio.com/products/visual-studio-community-vs)
  2. Download and extract the CRM 2015 SDK http://www.microsoft.com/en-us/download/details.aspx?id=44567
  3. Download and install .NET 4.5.2 Developer Pack http://www.microsoft.com/en-us/download/details.aspx?id=42637
  4. Download and extract this project
  5. Copy and overwrite from the CRM SDK …\SDK\Bin\Microsoft.Xrm.Sdk.dll to the project …\Source Code\ManipulationLibrary\sdk
  6. Open Visual Studio 2013 then open the solution …\Source Code\ManipulationLibrary.sln
  7. In the Solution Explorer right click “ManipulationLibrary” and select properties
  8. On the Application tab, change the Target framework to .NET Framework 4.5.2
  9. Select build from the menu bar and rebuild the solution
  10. Run the Plugin Registration tool from the CRM SDK …\SDK\Tools\PluginRegistration
  11. Create a new connection to your Office 365 environment
  12. Select register new assembly
  13. Load the DLL from your rebuilt solution …\Source Code\ManipulationLibrary\bin\Debug\ManipulationLibrary.dll
  14. You should see all the available workflows listed in step 2. Select Sandbox for step 3, and I left Database for step 4. Then click register selected plugins.

Note: Some of the Manipulation Library features may not work but he basic one works.

Advertisements

4 thoughts on “Manipulation Library for CRM 2015

  1. Ulrich April 3, 2015 / 12:32 am

    I try to mke it work for CRM 2013, any idea how this can be achieved?
    Thanks for any idea!

    Like

    • Mandar Joshi April 6, 2015 / 7:57 pm

      Similar approach should work for CRM 2013. Did you tried that? Unfortunately I do not have any CRM 2013 environment available for now to confirm that.

      Like

  2. BlueOcean January 6, 2017 / 10:28 pm

    Will this workaround also work for the CRM 2016?

    Like

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s