Ravishchandra Gupta's Blog

Hello Guys, In our previous  blog   we have explored how to use Form Component control. Today we will see how to use same control for regarding columns. Do follow us to know more about Dynamics and Power Platform.  Also if you like our blog then please comment and share this blog with your friends. Consider a scenario where we are using a phone call activity. As we know that we can create phone call activity for various records like contacts, accounts, cases etc. We have regarding columns for representing contact or account. Now we want to edit information of contact or account from phone call activity. In this situation we will be using Form Component control using regarding column. Let's see how to do that. In our previous blog, we have created Main form for account. Now we will be creating one main form for the contact also. As you can see we have form for contact. Now we will be configuring regarding column on phone call activity. As you can see, we have regarding col...

Hello Guys, In our previous  blog   we have explored how to generate table metadata using XRM toolbox. Today we will see how to use Form Component control. Do follow us to know more about Dynamics and Power Platform.  Also if you like our blog then please comment and share this blog with your friends. First of all we will what is Form component control. Form Component Control is one of the most important and useful features which allow us to see and edit data of the related entity on the main form. Consider a scenario, where we are  working on the contact record and we want to change some related information of a account then we can do it on the same form itself. Previously, if we wanted to edit the information of the account, we needed to open account record and then change the information. Previously, by using Quick View Form we could see the data of related records but we could not edit. But now using Form Component Control we can edit information of related ...

Hello Guys, In our previous  blog   we have explored how we can migrate CRM records from one environment to another using same GUID. Today we will see how to generate table metadata using XRM toolbox. Do follow us to know more about Dynamics and Power Platform.  Also if you like our blog then please comment and share this blog with your friends. Table metadata in D365 CRM plays a crucial role in managing and optimizing data storage, business logic, and application development. Below are some uses cases where we can use Table metadata: 1. Data Management and Governance Data Integrity: Enforce field-level constraints like data types, max lengths, and required fields. Data Validation: Maintain consistent data input by using metadata to define permissible values. Data Compliance: Ensure regulatory requirements are met by tracking metadata properties such as security roles. 2.   Reporting and Analytics Metadata-driven Reporting: Use metadata definitions to dynamic...

Hello Guys, In our previous  blog   we have explored some facts about business rules. Today we will see, how we can migrate CRM records from one environment to another using same GUID. Do follow us to know more about Dynamics and Power Platform.  Also if you like our blog then please comment and share this blog with your friends. There are many scenarios where we need to move crm records from one environment to another environment along with same GUID. We can use Data migration tool which are available in XRM toolbox. But we will use CRM Data import. Login to Destination Environment in which you want to import the Data with the same GUID. For example we have some contact records as shown below in Dev environment. Now we want to import these records on QA environment. So first of all open advance find and select the table as shown below: You can click on Edit column to select specific column which you want to be available in destination environment. Now click on Export Con...

Hello Guys, In our previous  blog   we have explored business rule. Today we will see some facts about business rules. Business Rules are used for implementing conditional functionalities like validation and pre-filled. The execution order of the business rule is as below: 1. System JS 2. Custom JS 3. Business Rules. If one Entity is having more than one Business Rule then order of execution depends on their activation. You can see the Rank of the Business Rule's execution order using Synchronous events execution order editor tool in XRM Toolbox. Consider a scenario, we have one table named Person as below: We have created two BR for some validation and prefill as shown below: The first BR is used to make the Last Name field mandatory and other one is used for setting full name based on first name. Now login to xrmtoolbox and open  Synchronous events execution order editor tool and select Person entity. Expand it and you see the rank of the BR. Basically BR rank depends ...