More recently I have been writing little bit more about data migration techniques and best practices. I have to say, it is a point where we all make mistakes. If you don’t map migrate the data properly, whatever the solution you may deliver, will not work. Especially when the current work of the client is dependent on existing data. If your CRM solution is not working, then you will get the blame no matter how good your solution is.
When providing client solutions with CRM, majority of the time clients want to migrate their existing data. The purpose of this article is to provide a comprehensive guide to migrate data with many to many relationships. As we all know support for many to many relationships is one of the coolest features in Dynamics CRM.
For instance, let’s assume a client wants to upload the accounts(companies) with the primary contact intact. In this scenario, accounts has a reference to contacts and contacts has reference to accounts (company). You can see the references in the below images.
On Dynamics 365 app market place, there is a app for Fields Services. This app is a great start point for clients who are in the field services industry. The out of the box application is ready to use. But, in some scenarios, need to convince your clients, that the solution is viable. You can easily install the app, but for your account manager or sales guys to go and demo the capabilities, you need demo data. You can’t do this with by out of the box sales data. You need field service specific data to give your prospects the feel of the application. The problem is, there is no proper guide given out there. The objective of this article is to provide step by step guide to install the demo data for Field Services.
Access teams is one of the cool features in Dynamics 365. This allows us to assign records to multiple users. An access team is basically a collection of users who has access to a record. For instance, there could be a large account, which a team of account managers might be working for continuous business.
There are many actions that you can perform against records. Following and un-following is one of them. This article is about a scenario where you can use this cool feature.
Assume that you have a list of clients or accounts. And you have nominated top 3 of those, because they bring the biggest chunk of your annual revenue. Above all they are your reference customers. Normally CEOs, Sales Directors would like to keep a close eye on these clients. With Dynamics CRM, they can easily follow these records. When they do that, these accounts will appear under the “Accounts I follow” view. So they don’t have to worry about all the accounts that exists in the system.
One of my previous articles, I have explained about how cool the Calculated Fields are. But, as always there is a catch, i.e. there are several limitations. So when you decide to use calculated fields, you need to remember these.
Dynamics CRM has the ability to assign users/teams with multiple security roles. This is ideal for medium to small scale organizations. Particularly, in scenarios where, within an organization there are no dedicated teams or individuals to perform certain tasks. Therefore set of business specific tasks can be shared among one or two individuals and the relevant security roles can be associated with the user(s).