Dynamics CRM on Nicolas Nowinski

Why the Microsoft Power Platform is the No-Code Low-Code Platform You Need Now

Sat, 01 Sep 2018 05:53:13 +0000

What is the Power platform all about? I get this question a lot.

The reality is that the Power platform is more than one thing and it can be “about” a lot of different things.

PowerApps is a pixel-perfect mobile-first UX app creation for the enterprise. Common Data Service is a ready-to-go no-limits data service for building an application backend. PowerApps is the ability to rapidly build forms and views over that data service with minimal effort. Dynamics 365 is a series of commercial applications ready to run your business processes. Power BI is about analyzing and visualizing data from anywhere. Flow is integrating data from multiple services and automating business processes across those services.

Dynamics CRM: Extensions to Improve IOrganizationService

Tue, 26 May 2015 22:42:41 +0000

I’ve become a big fan of extension methods over the years to make my development work in Dynamics CRM, easier to implement and easier to read (i.e., easier to support.) Extension methods allow us to, exactly as the name implies, extended an existing class or interface with new methods - its a simpler version of implementing a derived class.

Anyone familiar with developing .NET code for Dynamics CRM will be familiar with the IOrganizationService interface and its varied implementations. While in most cases I’m a fan of implementing my own version of IOrganizationService, often for code-base simplicity I’ll rely on some extension methods for my code.

Dynamics CRM: FetchXML to Retrieve Access Team Members

Tue, 19 May 2015 22:56:12 +0000

The very smart folks over at PowerObjects recently posted a blog article on how to retrieve the membership of an Access Team using SQL.

When working in CRM Online or when we need to use the query for a view we have to make our SQL statements work as FetchXML. Here is the FetchXML that will retrieve Access Team members. You can edit it for the desired entity and place filtering as appropriate. In this case, we are retrieving all the Opportunity records and User records for the Opportunity Sales Teams (CRM’s default OOTB example of Access Teams.)

Duplication Instead of Automation: Retailers Need Dynamics CRM

Wed, 08 Apr 2015 02:46:54 +0000

This evening I was at a major national electronics retailer to purchase a new television. I recently moved into a new place and needed a television sized appropriately for the room (and, my old television being plasma, something that would run cooler to save money on air conditioning.)

There was a very nice sales person - not too much pressure (and, being honest, didn’t know much about televisions) but there to help when I needed it. I had already done some research and really just needed to see a few models side-by-side to make a final decision. It probably didn’t take me more than thirty minutes to decide which television I wanted, at which point the sales person sprung into action.

Dynamics CRM and ILMerge: The Easy Way to Merge DLLs for Plugins

Mon, 02 Feb 2015 04:08:17 +0000

Being able to use external DLLs in Dynamics CRM plugins is challenging but doable. Most people who have been doing development on the Dynamics CRM platform for any period of time know that it is not enough to simply reference the DLLs in Visual Studio - you must somehow make them available to run on the server - this can range from mildly annoying to impossible (if you using CRM Online.)

Dynamics CRM: Custom Entity Forms Specific to Users

Mon, 10 Mar 2014 10:54:00 +0000

Recently a question was asked about creating forms and specifying a default form in Dynamics CRM that was limited to specific group of users. The original question and answer are available on Stackoverflow. Stackoverflow is a great site for asking and getting answers to your Dynamics CRM questions.

You already have a default form for the entity that is used by all users (All Users). You want to add an additional form to that entity that is only available to some of the users (Select Users). All Users are currently assigned a security role that gives them the necessary access to the system.

Using LINQPad for Dynamics CRM Development

Fri, 01 Nov 2013 00:46:54 +0000

You are likely already familiar with the excellent development tool LINQPad and if you are a Dynamics CRM Developer you, hopefully, are familiar with LINQPad Plugin for Dynamics CRM. Using LINQPad along with the LINQPad CRM Plugin is a great way to learn the ins and outs of writing LINQ queries for Dynamics CRM.

In this article I will show you how, with just a minimal of effort, you can start using LINQPad to directly call Dynamics CRM. This will allow you to go beyond just building LINQ queries and execute code to test Request/Response messages, QueryExpression retrieval, FetchXml, and much more. Using LINQPad allows you to test and learn in real-time without waiting to compile your code and execute your test cases (if you even have test cases! You do have test cases, right?)

Dynamics CRM 2011: Prep Plug-in for XrmToolbox

Thu, 31 Jan 2013 12:53:00 +0000

Originally published at http://goo.gl/bkewP1 I can’t really take a lot of credit for this post. All of the difficult work was done by a couple of Dynamics gurus. XRM Prep Plug-in This is a plugin for XrmToolBox (http://xrmtoolbox.codeplex.com/) by Tanguy Touzard. Great thanks to Tanguy for releasing XrmToolBox and providing really solid documentation on how to create Plug-ins for it. XrmToolBox and his numerous other very useful Dynamics CRM tools, which all now run in XrmToolBox, are a great value to the Dynamics CRM community. The idea, implementation logic, and solution file that are the basis for this plug-in are the work of Marc Schweigert from Microsoft. His excellent blogging has been the source of great education for me about how to get the most out of Dynamics CRM. The XRM Starter solution file and the code were published by him in the blog post linked to below. http://blogs.msdn.com/b/devkeydet/archive/2013/01/22/getting-a-new-crm-2011-organization-ready-for-xrm.aspx You must install XrmToolBox on your machine to use this plug-in (http://xrmtoolbox.codeplex.com/). After installing XrmToolBox copy the Procetrnix.CleanForXRM.Dll file to the same directory that XrmToolBox.Exe is installed. Run XrmToolBox and you should see the XRM Prep listed as one of the modules under the Home tab. This plug-in is intended to be used against a new Dynamics CRM organization prior to making any customizations to prepare it for custom development, it can perform the following: - Install the XRM Starter solution file from Marc’s post. Hide the existing reports. Remove all the non-required security roles. Remove the standard dashboards. There are four checkboxes that allow you to select what all you want XRM Prep to handle for you. If you do not want the solution file to be imported you should uncheck Import Solution, etc. When you are ready click on Run in the toolbar at the top of the tab to run the process. You’ll see a status screen while the work is being done and a message box will inform you when it is completed. If you want a copy of the solution file you may download it from the link in Marc’s blog article (URL above) or you can click the Export XRM Solution File from the toolbar to export the file. The DLL exposes a public class, XrmSolutionSetup, that can be used by any .NET 4.0 code. XrmSolutionSetup has a method called Execute that expects to be used as the delegate for BackgroundWorker.DoWork. Thus, this code could be reused in another solution if you did not want to use XrmToolBox. One idea would be to implement this in a console application or PowerShell script that deployed and configured a new organization to start development. Here is the plug-in DLL: http://sdrv.ms/11pTAIn If you want to modify it for your own purposes or just see how it was implemented here is the source:http://sdrv.ms/11pTMaB No guarantees or anything…the source code is there so make it do what you want it to do. I hope this will help you speed up development work and inspire a couple people to make use of the great platform that Tanguy has given us with XrmToolbox.

Dynamics CRM 2011: Finally...Enterprise ALM for Dynamics CRM 2011

Fri, 28 Dec 2012 16:42:00 +0000

Originally published at http://goo.gl/XXm6z5 I wanted to bring your attention to two items that can be very useful for all of us working on Dynamics CRM. As you are aware, CRM customization and development has never really worked well with enterprise focused application lifecycle management (ALM.) The export capability (even with Solutions in 2011) has never worked very well with source code control and change management. In addition, scripting of builds and deployments for customizations have never been what I would call straight-forward or even possible. In the SDK released for Rollup 10 a Solution Packager command-line application that takes an exported solution file and breaks it up into its individual pieces. This combined with the command-line Solution Export tool in the MSCRM Toolkit provides the pieces necessary to automate CRM solutions in a system such as TFS or Git. (http://intovsts.net/2012/12/28/integration-of-dynamics-crm-2011-solutions-with-tfs/) Of course, the next request in enterprise development is automated deployment. As a holiday gift to the CRM world ADXStudio released a beta of their ADXStudio ALM Toolkit (http://community.adxstudio.com/products/adxstudio-alm-toolkit/) - licensing and pricing have not been announced so we’ll have to wait and see. This toolkit includes PowerShell Scriplets that allow for creating organizations and user and automated deployments of solutions, it includes a number of PowerShell scripts to demonstrate usage. It also includes a very valuable command-line tool to copy data from a source system to a file and then import the data during a deployment – this is especially useful for simplifying the process of loading configuration/base data during deployment. Taken together these tools provide the pieces necessary to fully automate the build and deployment process for Dynamics CRM. Many environments do not need this level of automation and the overhead for these tools has to be justified by the requirements. That said, for those environments where the needs justify the time/expense of full ALM it is good to know the requirements can be met with using pre-built tools.

Dynamics CRM 2011: Simplifying the Request Response Model

Sat, 22 Sep 2012 16:40:00 +0000

Originally published at http://goo.gl/C1n3Hw If you have worked with the Dynamics CRM 2011 SDK you are probably very familiar with the Request/Response model messages in Microsoft.Crm.Sdk.Messages. As a developer trying to write good code I always want to wrap any service call in a Try/Catch statement to provide proper error handling. Another goal is to keep the code as neat as possible for when I – or someone else – has to go back and read it. Wrapping calls in Try/Catch statements increases the total lines of code it takes to implement functionality and makes the code more difficult to read. Recently I was working on a project where I had several of these calls in a row: Execute a request, process the response, build a new request, execute, etc. etc. While I was looking at the code I realized that my catch routine was basically the same (format a message for the user and exit out of the program – in addition to sending a number of execution details to the tracing service). Since the code was getting very long, my first thought was to refactor each of these calls into its own method. While this approach would make my code a bit cleaner, it was still somewhat limited in value. After thinking about the problem a bit more, I decided this would be a perfect opportunity to implement generics, extension methods, and delegates. If you are unfamiliar with any of these topics, here is a super quick introduction: - Generics allow us to create a method without having to know all the input types or the response type thus allowing the developer to specify them when calling the method. Extension methods allow us to create static methods against an existing class without having to inherit to a new class thus we do not disturb any code already relying on the class we want to extend. Delegates let us take a method (that matches the specified signature) and pass it as a variable. You can find out more about each of these concepts in the MSDN documentation links provided. Before we get too far into the details we should review the issue we are trying to resolve. Here is a very basic CRM plug-in that executes a WhoAmI request and gets a WhoAmI response. As I count it there are 6 statements with the try/catch but not including the PluginSetup (see my previous post athttp://goo.gl/lEaa9), to complete the request. It may not seem like a lot, but in the real-world those calls also have logging and the request probably has actual properties that need to be set. No matter what request message you use the basic pattern will remain the same. public void Execute(IServiceProvider serviceProvider) { var p = new PluginSetup(serviceProvider); var req = new WhoAmIRequest(); WhoAmIResponse response = (WhoAmIResponse)p.Service.Execute(req);