Business process flows are not a new feature in Dynamics CRM 2015. They were introduced in the 2013 release as a way to provide a step by step guide to completing some process. The business process flow could be step up as a series of stages, with each stage containing multiple steps. The steps provide the user with a visual indicator of where in the process they are.[More]
Have you ever wondered how you are authenticating to your CRM application? It is useful to think about this because it:[More]
The Xrm.Page.data.process namespace has been introduced in the SDK of Microsoft Dynamics CRM 2015, which provides events, methods, and objects to interact with the business process flow data in a form.[More]
Tags: CRM 2015
This is a fairly new feature to CRM Online, There is a bit more than just turning it on to get it to work.[More]
I wanted to cover a simple process that is now available in CRM Online that integrates CRM Online to SharePoint Online. Microsoft has replaced the traditional CRM List Components that was used to link MS CRM and SharePoint. It is so simple to configure that it can be a bit misleading. So this blog entry is meant to simplify the process. First you will need to make sure that you have configured a site collection before you begin the Server Side configuration process. It’s been my experience that these integrations work best at the root of a site collection.
https://wfdemosite.sharepoint.com is the URL of the site that I am going to integrate with CRM Online.[More]
The Integration User is allowed to update Sales records such as Orders when they are in a read-only Submitted state. This user is deployed out of the box in Microsoft Dynamics CRM and can only be accessed programmatically. You can see the INTEGRATION user by doing an advanced find on disabled users. The following example will demonstrate how to “impersonate” the INTEGRATION user and assumes that your organization is using a 3rd party application such as an ERP or Finance system and has SOP Integration Mode turn on.
Scenario: There’s integration between CRM and a 3rd party system that pushes Orders from CRM when the status is changed to Submitted. Users in CRM would like to make changes to the Order record after it’s been submitted but cannot edit the fields on the form because the record is read-only.[More]
So you have Dynamics CRM up and running and now it is time to re-create and re-type all of those contacts, tasks, appointments, and emails. Well let’s consider some other options first. In particular let’s take a look at new and existing features provided by the CRM development team, namely, Server-Side Synchronization, Email Router and CRM for Outlook. Depending on the existing infrastructure only Email Router and CRM for Outlook might be available. There is a really nice chart on the supported configurations located here. Basically Server-Side Synchronization is not available for hybrid deployments (CRM Online to Exchange on-premises and vice versa). There are some other limitations listed in the TechNet article.
Despite the limited availability Server-Side Synchronization is the easiest out of the three options to setup and the most convenient one as it doesn’t require any additional software at all. So let’s get started.
Dynamic or “dependent” pick lists have been a challenge to implement in CRM since the beginning of time (CRM time that is). You know, select option 1 from the parent pick list and the options available in pick list 2 change. Traditionally it has taken hundreds (sometimes thousands) of lines of code to implement this functionality, especially where the number of available options runs into the hundreds. Once implemented, it often became a developer’s nightmare to add/modify or change options.
Our own Chuck Oldes posted a blog article a little while back showing how to implement a dependent pick list utilizing the code sample provided by Microsoft in the SDK. A nice approach to be sure, but still requires a good deal of XML manipulation.[More]
It is a well-known best practice to not do any customization to CRM directly in the Default Solution, but alas, it is so easy to find yourself there! We all run into solutions with the dreaded “new_” prefix to entities and attributes. This article will discuss a method that will allow you to take an unmanaged solution and refactor it to use a custom prefix and publisher.
First, make sure the solution you are working with is not the Default solution – these steps must be taken against a separate solution (unmanaged). After that, you will need to unzip the package to uncompressed files. Once the files and subfolders are uncompressed, you’ll need to open the solution.xml, customizations.xml and [Content_Types].xml files in an XML editing application similar to Visual Studio.[More]
"What kind of ROI can I expect from the new CRM system?" My client's boss asked, "Do you think we're on track to see a return in a year or less?"[More]
In my blog post from September, 2013 (http://blog.webfortis.com/crm-2013-rules) I described my excitement for the new feature in Dynamics CRM 2013, Business Rules. Fast forward a year-and-a-half and I thought I would share the latest caveat I discovered with Business Rules and its conspicuously absent error notification.[More]
In the world of consulting, documentation can become a thing of misery for both authors and readers. This is because most organizations who produce documentation strive toward efficiency by using templates and samples. It is also because most clients expect little to no actual value from documentation delivered from consultants. On both sides it becomes a "necessary evil". So why bother?[More]
A new year is often the impetus for organizations to embark on a new start. I see this with almost every project I work on to some degree or another. The mentality is a good one and it comes with the right end game in mind - usually.[More]
As a CRM Consultant, I often get requests from clients to auto-populate data whenever the expected value is known. There may be several key fields from the parent record that need to be displayed on the child record, but they don’t want the end user to have to re-key the same data.
No problem - just create a 1:N Relationship and then add a mapping for each of the fields you want displayed on the child record. Easy enough, right? Right, except that the client’s request often comes with an assumption. Clients often assume that the mapped data is dynamically updated. Not so. The data is only pushed down to the child record when the child record is first created, but it does not display any updates that may be made to the parent record in the future.[More]