When it comes to testing business applications implemented with Dynamics CRM, sometimes you might have to bring down your production data to your Development, Testing, UAT/Pre Production environments. In such scenarios, what if your company policies does not allow you to play around with sensitive data of their clients. For instance, a tester might trigger several email to a client for testing certain functionality which will surprise the client and some may not like it at all.
Therefore, it is always good to replace sensitive data with dummy data values. But this is not a simple task to do if you have large quantities of data. One might argue that for testing, you may not require large quantities of data. But, if the testers are doing performance testing, then large quantities of data is required.
Objective of this article is to highlight options available to replace/scramble sensitive data with dummy data.
XRM Tool Box has this cool plugin to clone entity metadata. I wanted to create an entity similar to the out of the box contact entity. This should have all the out of the box fields and few additional fields. The design decision to clone the Contact entity rather than using the existing one was:
Contact entity was used for other requirement to store information about individuals.
Cloning the contact entity will have more diverse entity structure
Maintain simplicity, where if I used the Contact entity for storing both type of records, the design would be more complex, leading to maintenance overhead in the future.
Hello readers. In this article, I am going to explain few facts about Dynamics 365 auto-numbering feature. Previously we had to write some SDK code to generate the auto numbering for custom entities. But after version 9.X, this is possible for any entity. I have been commissioned to find solution to replace the custom written auto numbering solution. From the team, this came up and had the opportunity to explore it more. You can find more details about this feature from the following link.
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.
Data migration is one of the top priority tasks in Dynamics 365 solutions. For majority of clients they have some data to be migrated to the new solution. And every client want their data to be perfect. So it is highly important that data is well prepared before doing any imports. Objective of this article is to highlight some of the best practices that you should follow up when preparing data.
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.
Out of the box, Dynamics CRM provides us set of reports. This article will talk about Case Summary Table reports which is significantly important for case management scenarios. In fact it is capable of highlighting the trends and patterns of cases that you are receiving for your products and services.