Monday, August 28, 2023

Filter Lookup Records in Dynamics 365 | Power Platform

How to filter lookup records in Dynamics 365?

Scenario: Imagine you have a list of cases in an Opportunity form, and you click on a field called "Case." Right now, it shows all cases, including the ones that are no longer active. But I only want to see the cases that are still active, not the inactive ones. So, we'll set it up to only show the active cases. You can do the same with other filters if needed.

Follow the video below to see the implementation.




Filtering a lookup field in a Dynamics 365 form allows you to restrict the choices available in the lookup based on certain criteria. This can be particularly useful when you have a large dataset and want to help users find and select the right record quickly. You can use multiple filter criteria by clicking the "Add Condition" button in the "Add Custom Filter" dialog, allowing for more complex filtering conditions.

Prerequisites:
Before we begin, make sure you have the necessary permissions to customize forms in Dynamics 365. You should also have a basic understanding of how to navigate and use the Dynamics 365 platform.

Steps to Set Up a Filtering Condition for a Lookup Field to Display Only Active Cases:

1. Log in to Dynamics 365:
   Start by logging in to your Dynamics 365 account with the appropriate credentials.

2. Navigate to the Opportunity Entity:
   Go to the area where your opportunities are managed and locate the Opportunity entity.

3. Customize the Opportunity Form:
   - Click on "Settings" (represented by a gear icon) in the upper-right corner.
   - Select "Advanced Settings."
   - In the new window, choose "Customizations" and then "Customize the System."

4. Edit the Opportunity Form:
   - In the Solution Explorer, expand "Entities" and select "Opportunity."
   - Under "Forms," find and select the form you want to customize (typically "Main Form").
   - Click on "Form Properties" in the ribbon.

5. Add a Subgrid for Case:
   - In the form designer, locate where you want to add the list of cases.
   - Drag and drop a "Subgrid" control onto the form.

6. Configure the Subgrid:
   - After adding the Subgrid control, double-click it to configure its properties.
   - In the "General" tab, choose the "Cases" entity as the data source.

7. Set the Filter Criteria:
   - In the "Data" tab of the Subgrid properties, scroll down to "Add Predefined Filter" and click on it.
   - Define a filter criteria that displays only active cases. For example, you can set the "Status Reason" field to "Active."
   - Save and close the Subgrid properties.

8. Publish Customizations:
   After configuring the Subgrid, make sure to save and publish your customizations.

9. Test the Form:
   Go back to your Opportunity entity and open an opportunity record. You should now see a list of cases related to that opportunity, filtered to display only the active cases.

Conclusion:
Customizing Dynamics 365 forms to display specific information, like showing only active cases in an Opportunity form, can greatly enhance your organization's efficiency and user experience. By following the steps outlined in this blog post, you can easily set up a filter condition to meet this requirement and ensure that your team works with the most relevant data.

Thursday, August 24, 2023

Introduction to Dynamics 365 Solutions

In Dynamics 365, a solution is like a special package that helps you change and improve the software to match what you want. It's a bit like using different tools to customize a toy to your liking. Solutions make it simple to share these changes with others and keep everything organized. It's like a recipe to make Dynamics 365 work exactly how you need it to!

Embracing Extensibility

Imagine the canvas of Dynamics 365 stretching before you, ready to be painted with innovation. Solutions are your palette. You can extend the power of Dynamics 365 Customer Engagement using solutions, either by directly importing applications with native components or creating installers for those with external components.

Harmony in Versions

Navigating the journey between Dynamics 365 versions becomes a breeze with solutions. Migrating your solutions? No problem. The compatibility chart guides you, allowing solutions to gracefully journey through versions and service pack releases.

Components, the Building Blocks

Solutions are about crafting excellence. Enter solution components – the artisans shaping the Dynamics 365 landscape. From customizable tools to APIs, the arsenal at your disposal is vast. And remember, solutions can only add and overwrite components, not erase them.

What Are Solutions and Why Should You Care?

Solutions are like toolkits that let you add new things to Dynamics 365 or change how it works. They're super useful because they help you share your cool creations with others.

Different Kinds of Solutions:

There are two types of solutions - think of them like two flavors. One flavor is "managed," which is like a ready-to-use package, and the other is "unmanaged," which is like a work-in-progress package.

Managed vs. Unmanaged

Picture solutions as dancers on the stage of innovation. Managed solutions, polished and complete, take the spotlight. Unmanaged solutions, the choreographers, are in development. Each dance, whether managed or unmanaged, affects the ultimate symphony of Dynamics 365's behavior.

The Maestro: Solution Publisher

Every masterpiece needs a maestro. In our story, that's the solution publisher. It provides the harmonious prefix for customizations and option values. Managed solutions dance to its tune for distribution and updates, creating a melody of organization-wide coherence.

Managed Properties: Sculpting Customization

Just as a sculptor molds clay, solution creators mold managed properties. These properties decide what's customizable in your solutions. Our guide unveils the secret behind locking down definitions for stability or keeping the door open for future changes.

Conflict Resolutions: The Art of Balance

Where solutions thrive, conflicts may arise. Our guide hands you the brush to paint resolutions. Merge or top wins? The canvas of user interface components unveils strategies to keep your Dynamics 365 masterpiece harmonious.

Dependencies: Threads of Unity

In the grand tapestry of Dynamics 365, dependencies weave threads of unity. Our guide explains how they ensure the system's integrity. Deleting, exporting, or importing, you'll be well-versed in preserving the harmony.

Linguistic Elegance: Multilingual Mastery

Dynamics 365's multilingual prowess elevates your solutions. Language packs add a symphony of languages to user interface elements. Our guide showcases how to seamlessly conduct this linguistic orchestra. 

Wednesday, August 23, 2023

Auto Populate and Concatenate Field using Processes | Dynamics 365

How to Auto Populate and Concatenate Field using Processes in Dynamics 365?


Follow the video below to see the implementation.


In Dynamics 365, you can use processes to automate various tasks, including auto-populating fields. The process automation tool in Dynamics 365 is known as Power Automate (previously known as Microsoft Flow). Power Automate allows you to create workflows that can automate actions and trigger processes based on certain conditions.

Updating with a detailed process with a snapshot soon...

Sunday, August 20, 2023

Auto Populating Field using Business Rule | Dynamics 365

How to Auto Populate Field using Business Rule in Dynamics 365?

Follow the below video to see the full implementation-
In Dynamics 365, a Business Rule is a tool that allows you to define and apply logic to automate and customize the behavior of your CRM system. It lets you set up conditions and actions without writing code, enabling you to create a set of if-then-else statements to guide user interactions and data manipulation. Business Rules are particularly useful for enforcing data validation, controlling field visibility, and triggering automatic field value changes based on user input or other conditions.

By combining conditions and actions, you can do any of the following with business rules:

  • Set field value
  • Clear field values
  • Set field requirement levels
  • Show or hide fields
  • Enable or disable fields
  • Validate data and show error messages
  • Create business recommendations based on business intelligence.

Set up an Auto Populating Field with a Business Rule in Dynamics 365:

Make sure that you have the System Administrator or System Customizer security role or equivalent permissions.

1. Access Business Rules:
Log in to your Dynamics 365 instance and navigate to the entity (record type) where you want to create the Business Rule.

Open solution explorer.

2. Create a New Business Rule:

   - In the entity's customization area, go to the "Business Rules" section.

   - Click on "New" to create a new Business Rule.


The Business Rule designer window opens with a single condition already created for you. Every rule starts with a condition. The business rule takes one or more actions based on that condition.



3. Define Conditions:

-Drag the Condition component from the Components tab to a plus sign in the designer.

-To set properties for the condition, click the Condition component in the designer window, and then set the properties in the Properties tab on the right side of the screen. As you set properties, an expression is created at the bottom of the Properties tab.

-To add an additional clause (an AND or OR) to the condition, click New in the Properties tab to create a new rule, and then set the properties for that rule. In the Rule Logic field, you can specify whether to add the new rule as an AND or an OR.

-When you're done setting properties for the condition, click Apply.

4. Add Actions:

   - Under the "Actions" section, add an action that will be triggered when the condition is met.

   - Select the action type "Set field value" to populate a field automatically.

   - Choose the target field you want to populate and set its value based on your predefined condition.

5. Define Actions and Values:

   - For the selected field, set the value you want to populate when the condition is met. This could be a fixed value, a formula, or a value from another field.

6. Apply and Publish:

   - Save your Business Rule configuration.

   - Publish the changes for the entity to make the Business Rule active.

7. Test the Business Rule:

   - Create or edit a record in the entity you configured the Business Rule for.

   - Input the necessary data to meet the condition you defined in the rule.

   - Verify that the target field is automatically populated based on the condition you specified.

8. Adjust and Fine-Tune:

   - If needed, revisit the Business Rule settings to adjust conditions, actions, or values.

   - Test the rule thoroughly with different scenarios to ensure it works as expected.

It's important to note that the exact steps might vary slightly based on the specific version of Dynamics 365 you are using and the customization options available in your instance. Always refer to the official documentation or user guides provided by Microsoft for detailed and up-to-date instructions.




Wednesday, August 16, 2023

Interview questions for Dynamics 365 Developer

Interview questions for Dynamics 365 developer role for 2+ year experience

1. Basic Interview Questions

2. More Technical Questions

3. Plugin Question with code

(Scroll Down for Answers)

1. Basic Interview Questions

**Dynamics 365 Technical Expertise:**

1. Can you explain the difference between Dynamics 365 CE (Customer Engagement) and Dynamics 365 Finance and Operations?

2. What are plugins and how are they used in Dynamics 365?

3. Describe the purpose of Business Process Flows in Dynamics 365 and how you've utilized them in your previous projects.

4. How do you handle data migration and integration tasks in Dynamics 365 projects?

5. Explain the concept of custom entities and how you've designed and implemented them.

6. What are Web Resources in Dynamics 365? Provide examples of scenarios where you've used them effectively.

7. How do you ensure security and data privacy within Dynamics 365 applications?

**Development and Customization:**

1. Can you walk us through your process of designing and implementing custom workflows in Dynamics 365?

2. Describe your experience with creating and maintaining custom reports and dashboards in Dynamics 365.

3. Have you worked with JavaScript and TypeScript in Dynamics 365 development? Give examples of how you've used client-side scripting to enhance user experience.

4. How do you approach designing and implementing solutions that involve both on-premises and cloud-based Dynamics 365 instances?

5. Have you integrated Dynamics 365 with external systems? What tools or methods have you used for this?

6. Explain how you handle version control and deployment in Dynamics 365 projects.

7. Can you discuss an instance where you had to optimize the performance of a Dynamics 365 application? What approaches did you take?

**Problem Solving and Troubleshooting:**

1. Describe a challenging bug or issue you encountered in a Dynamics 365 project and how you went about identifying and resolving it.

2. How do you approach debugging and diagnosing issues in a Dynamics 365 environment?

3. Have you worked with Azure DevOps or similar tools for managing Dynamics 365 projects? Describe your experience.

4. What strategies do you use to ensure the reliability and availability of a Dynamics 365 application during updates and maintenance?

**Communication and Collaboration:**

1. Can you provide an example of a situation where you had to communicate technical concepts to non-technical stakeholders?

2. How do you collaborate with functional consultants, business analysts, and other team members in a Dynamics 365 project?

3. Describe a time when you had to manage conflicting priorities or requirements within a Dynamics 365 development project.

**General Knowledge:**

1. What are the latest updates or features in the most recent version of Dynamics 365? How do they impact development?

2. How do you stay updated with the latest trends and best practices in Dynamics 365 development?

3. Can you discuss any experience you have with Microsoft Power Platform and its integration with Dynamics 365?

--------------------Answers --------------------

**Dynamics 365 Technical Expertise:**

1. Dynamics 365 CE focuses on customer relationship management, while Dynamics 365 Finance and Operations deals with enterprise resource planning. CE handles sales, customer service, and marketing, while Finance and Operations manage financials, supply chain, and manufacturing.

2. Plugins are custom code snippets that extend the functionality of Dynamics 365. They are triggered by specific events and can interact with data and perform actions, allowing for custom business logic.

3. Business Process Flows guide users through predefined processes, ensuring consistent and organized data entry and interactions. For instance, I used them to streamline lead-to-opportunity processes.

4. Data migration involves transferring data from one system to another, often using tools like Data Import Wizard or Data Migration Assistant. Integration involves connecting Dynamics 365 with external systems, usually utilizing APIs and middleware.

5. Custom entities are data structures tailored to specific business needs. I've designed custom entities for specialized objects like equipment, projects, or events.

6. Web Resources are files like HTML, JavaScript, or CSS that can be used in Dynamics 365 forms, dashboards, and other areas to enhance user experience and functionality.

7. Security roles, field-level security, and record-based security are methods to control access to data in Dynamics 365, ensuring that users see only what they're authorized to.

**Development and Customization:**

1. Custom workflows automate business processes by defining a series of steps. I've used them to automate lead qualification and approval processes.

2. I've used tools like Power BI to create custom reports and dashboards in Dynamics 365, providing insights into sales trends and customer interactions.

3. Yes, I've used JavaScript to enhance the client-side functionality of Dynamics 365 forms. For example, I've implemented form validation and dynamic field updates.

4. For hybrid environments, I've integrated on-premises Dynamics 365 instances with the cloud using Azure Service Bus or Azure Logic Apps for data synchronization.

5. I've integrated Dynamics 365 with external systems using RESTful APIs and Azure Logic Apps. For example, syncing customer data between Dynamics 365 and a marketing automation platform.

6. I use solutions and version control tools like Azure DevOps to manage changes and deployments in Dynamics 365 projects, ensuring a controlled release process.

7. I optimized performance by using caching mechanisms, optimizing queries, and minimizing the use of synchronous plugins. For larger datasets, I employed batch processing.

**Problem Solving and Troubleshooting:**

1. In one project, a synchronization issue caused data discrepancies between Dynamics 365 and an external system. I debugged the integration code, identified the root cause, and applied necessary adjustments to ensure data consistency.

2. I use platform tracing and debugging tools to identify issues. I follow a systematic approach, analyzing error messages, reviewing logs, and isolating the problematic code.

3. I've used Azure DevOps to manage project tasks, code repositories, and continuous integration/continuous deployment (CI/CD) pipelines, enabling seamless collaboration among team members.

4. During updates, I ensured high availability by utilizing rolling updates, performing thorough testing in a staging environment, and monitoring the system closely after deployment.

**Communication and Collaboration:**

1. I conveyed complex technical concepts to non-technical stakeholders by using clear analogies and visual aids, focusing on the business impact of the technology.

2. I collaborate with functional consultants to understand business requirements and translate them into technical solutions. Regular meetings and shared documentation help maintain alignment.

3. When facing conflicting priorities, I initiate open discussions with stakeholders, emphasizing the importance of balancing immediate needs with long-term system integrity.

**General Knowledge:**

1. In the latest version, Dynamics 365 introduced AI-powered insights, enhanced integration with Microsoft Teams, and improved mobile experiences, among other features.

2. I stay updated by attending conferences, participating in online communities, and reading Microsoft's official documentation and blogs.

3. I have experience with Power Platform components such as Power Apps and Power Automate, using them to create custom solutions that extend Dynamics 365's capabilities.

2. More technical questions

**Dynamics 365 Customization and Development:**

1. Explain the differences between real-time workflows and asynchronous workflows in Dynamics 365. When would you choose one over the other?

2. How do you register a custom plugin in Dynamics 365? Can you provide an example of a scenario where you've used a plugin to extend functionality?

3. What is the purpose of the FetchXML query in Dynamics 365? Provide an example of a situation where you would use FetchXML.

4. How would you implement client-side validation for a specific field on a Dynamics 365 form? What are the advantages of using client-side validation?

5. Describe your experience with Business Rules in Dynamics 365. When would you use Business Rules versus plugins or custom code?

6. How do you secure sensitive data in Dynamics 365? Explain the process of implementing field-level security for specific records.

**Integration and Custom Web Resources:**

1. Can you outline the steps to create a custom Web API endpoint in Dynamics 365? What are some scenarios where you might use a custom Web API?

2. Discuss the process of integrating Dynamics 365 with an external service using Azure Logic Apps. What considerations should be taken into account?

3. How would you embed a custom HTML web resource into a Dynamics 365 form? Provide an example of how you've used custom web resources to enhance user experience.

4. Explain the purpose of virtual entities in Dynamics 365. How would you set up a virtual entity to display data from an external system?

**Performance Optimization and Troubleshooting:**

1. What are some techniques you've used to improve the performance of Dynamics 365 forms and views, especially in scenarios with large datasets?

2. Describe a situation where you encountered a plugin causing a performance bottleneck. How did you identify and address the issue?

3. How would you approach troubleshooting a situation where a Dynamics 365 workflow isn't firing as expected? What tools or methods would you use?

**Advanced Dynamics 365 Concepts:**

1. Explain the concept of Business Process Flows branching and stages in Dynamics 365. How have you implemented complex branching logic in your projects?

2. What are Business Units in Dynamics 365? How can they be utilized to manage security and data access in a complex organization?

3. Describe the use of Power Automate (previously Microsoft Flow) in Dynamics 365 integration scenarios. Provide an example of a flow you've created.

--------------------Answers --------------------

**Dynamics 365 Customization and Development:**

1. Real-time workflows execute immediately after a specified event occurs, while asynchronous workflows are queued for background processing. Choose real-time workflows for immediate user interaction and asynchronous workflows for non-urgent, background processes like sending emails.

2. To register a custom plugin, you create a class that implements the IPlugin interface, compile it into a DLL, and then use the Plugin Registration Tool to deploy it to Dynamics 365. An example scenario could be a plugin that triggers on opportunity creation to validate data and perform additional calculations.

3. FetchXML is a query language used to retrieve data from Dynamics 365. An example scenario is querying for all accounts where the industry is "Technology" and the revenue is greater than $1 million.

4. Client-side validation can be implemented using JavaScript. You attach an event handler to the field's onchange event, perform validation logic, and provide user-friendly error messages. Client-side validation reduces server round-trips and provides instant feedback to users.

5. Business Rules are used for simple form logic without writing code. For complex logic or scenarios requiring data manipulation, plugins or custom code are preferable.

6. Field-level security restricts access to specific fields for certain users or teams. You enable field-level security, define security profiles, and associate them with users or teams. This prevents unauthorized users from viewing or modifying sensitive data.

**Integration and Custom Web Resources:**

1. To create a custom Web API endpoint, you define a Web API function in a custom action, create a custom plugin to handle the action, and then expose it through the Web API. An example scenario could be creating a custom Web API to retrieve related contact information for an account.

2. Integration using Azure Logic Apps involves creating a workflow that connects to Dynamics 365 and external systems through connectors. Considerations include authentication, error handling, and data transformation.

3. To embed a custom HTML web resource into a Dynamics 365 form, you create an HTML file and upload it as a web resource. You then reference this web resource within the form. An example scenario could be embedding a custom map visualization using HTML and JavaScript.

4. Virtual entities allow you to view and interact with external data in Dynamics 365 without physically storing it. You set up a connection to the external data source, define the entity structure, and map attributes. For instance, you could use a virtual entity to display recent social media posts related to an account.

**Performance Optimization and Troubleshooting:**

1. Techniques to improve form and view performance include optimizing fetch queries, using filtered views, enabling caching, and minimizing the number of visible fields and columns. Implementing asynchronous plugins and leveraging data virtualization also help.

2. If a plugin causes performance issues, I'd start by profiling the plugin's execution time and resource usage. I'd review the plugin logic for any unnecessary actions, database queries, or loops that could be optimized. Profiling tools like XrmToolBox's Plugin Trace Viewer can be valuable.

3. Troubleshooting a workflow involves checking the workflow's activation conditions, logic, and related data. Using the built-in workflow tracing and enabling tracing in the Dynamics 365 settings can provide insights into why the workflow isn't firing as expected.

**Advanced Dynamics 365 Concepts:**

1. Business Process Flow branching allows different paths based on conditions. Stages represent a phase within the process. Complex branching can be achieved by defining multiple paths within stages and using conditional branching at the stage level.

2. Business Units in Dynamics 365 are logical containers that help organize data and security settings. They're useful for managing different divisions or departments within an organization. Security roles and data access can be configured based on the business unit hierarchy.

3. Power Automate can be used to automate processes across different systems, including Dynamics 365. An example flow could automate lead-to-opportunity conversion by triggering a flow when a new lead is created and then creating a corresponding opportunity in Dynamics 365.

These answers aim to showcase a deep understanding of the technical aspects of Dynamics 365 development and customization. Keep in mind that you can elaborate further based on your own experiences and project contexts.


3. Plugin Question with code

1. On Opportunity form

  1. When the Opportunity is saved do a simple check using Plugin that Customer’s Monthly Salary is Defined and is more than $5,000.

  2. Create a field Monthly Income of type currency on the Contact entity to capture its Monthly Salary.

  3. If the Salary is less than $5,000, then the Opportunity should not be created.


2. To create a plugin for a button that enables bulk edit of records in Dynamics 365, you can follow these general steps: (chatgpt solution)
  • Create a custom button on the entity form where you want to enable bulk edit.
  • Create a new plugin using Visual Studio or any other development tool that supports .NET framework and the Dynamics 365 SDK.
  • In the plugin code, define the steps to retrieve the records to be bulk edited, and perform the desired operations on those records.
  • In the plugin registration tool, register the plugin to execute when the custom button is clicked.

3. Pre-populate field

4. Plugin to update all the related contacts of a specific account when a specific field on account record has been updated

Description: Following are the details of what needs to be covered:

  1. Make sure we have Account to Contact (1:N) relationship setup calling the subgrid as

Related Contacts

  1. Create a new field in Account and Contact both called as “Payment Type” which is an

optionset field having options as {Cash, Debit Card, Credit Card}

  1. Create a plugin on the Account entity which will be registered on the “Update” of the “Payment Type” field.

  2. Plugin logic will include the following steps:

  1. Retrieve all related Contacts corresponding to Account in context

  2. Update “Payment Type” field on all the Contacts same as what has been set on

the updated Account record


Plugin code


-----------------------------------------1----------------------------------------



-----------------------------------------2----------------------------------------

using Microsoft.Xrm.Sdk;

using Microsoft.Xrm.Sdk.Query;

using System;


namespace MyPluginNamespace

{

    public class BulkEditPlugin : IPlugin

    {

        public void Execute(IServiceProvider serviceProvider)

        {

            // Obtain the execution context from the service provider.

            IPluginExecutionContext context = (IPluginExecutionContext)serviceProvider.GetService(typeof(IPluginExecutionContext));


            // Check if the plugin is executed from the custom button click event.

            if (context.MessageName.ToLower() != "my_custom_button_name")

                return;


            // Obtain the organization service from the service provider.

            IOrganizationServiceFactory serviceFactory = (IOrganizationServiceFactory)serviceProvider.GetService(typeof(IOrganizationServiceFactory));

            IOrganizationService service = serviceFactory.CreateOrganizationService(context.UserId);


            // Define the query to retrieve the records to be bulk edited.

            QueryExpression query = new QueryExpression("my_entity_name");

            query.ColumnSet = new ColumnSet(true); // Include all columns.

            // Add any necessary conditions to limit the records to be edited.

            // For example, you might want to retrieve only records that meet certain criteria or that belong to a certain view.


            // Retrieve the records to be edited.

            EntityCollection results = service.RetrieveMultiple(query);


            // Perform the bulk edit operations on each retrieved record.

            foreach (Entity record in results.Entities)

            {

                // Update the record as needed.

                // For example, you might want to set a field value, clear a field value, or perform some other operation.

                // You can use the service.Update() method to update the record in the database.

            }

        }

    }

}


Note that you will need to replace my_custom_button_name with the name of your custom button, and my_entity_name with the name of the entity you want to bulk edit. You will also need to add any necessary conditions to the query to retrieve only the records you want to edit. Finally, you will need to test the plugin thoroughly to ensure that it behaves as expected and does not cause any unintended side effects.



-----------------------------------------4----------------------------------------

using System;

using System.Collections.Generic;

using System.Linq;

using System.Text;

using System.Threading.Tasks;

using Microsoft.Xrm.Sdk;

using Microsoft.Xrm.Sdk.Query;

namespace KervDemo

{

    public class UpdatePaymentTypeInAssociateContact : IPlugin

    {

        public void Execute(IServiceProvider serviceProvider)

        {

            ITracingService tracingService = (ITracingService)serviceProvider.GetService(typeof(ITracingService));

            IPluginExecutionContext context = (IPluginExecutionContext)serviceProvider.GetService(typeof(IPluginExecutionContext));

            IOrganizationServiceFactory serviceFactory = (IOrganizationServiceFactory)serviceProvider.GetService(typeof(IOrganizationServiceFactory));

            IOrganizationService crmService = serviceFactory.CreateOrganizationService(context.UserId);


            if (context.InputParameters.Contains("Target") && context.MessageName.ToUpper() == "UPDATE")

            {

                Entity entity = context.InputParameters["Target"] as Entity;

                

                OptionSetValue paymentTypeValue = entity.Attributes.Contains("kerv_paymenttype") ?

                    entity.GetAttributeValue<OptionSetValue>("kerv_paymenttype") : null;

                int paymentType = paymentTypeValue.Value;

                //Fetch Contact Records using Query Expression


                QueryExpression qe = new QueryExpression("contact");

                qe.Criteria.AddCondition("parentcustomerid", ConditionOperator.Equal, entity.Id);

                EntityCollection relatedContacts = crmService.RetrieveMultiple(qe);

                if(relatedContacts != null && relatedContacts.Entities.Count > 0)

                {

                    foreach(var contact in relatedContacts.Entities)

                    {

                        Entity entity = new Entity(contact.LogicalName, contact.Id);

                        entity1["kerv_paymenttype"] = new OptionSetValue(paymentType);

                        crmService.Update(entity1);

                    }

                }

            }

        }

    }

}



Tuesday, August 15, 2023

Create Trial Instance in Dynamics 365

Q. How to create Create Sales Trial Instance in Dynamics 365?

Follow the below video to see the full implementation-

A trial instance refers to a temporary environment that allows users to explore and evaluate the features and capabilities of the Dynamics 365 applications It's a way for organizations to test the software, understand its functionality, and determine if it meets their specific business needs before deciding to subscribe to a paid version. 

This lets them understand how the program functions and if it fits their needs before they decide to pay for it. They can play around with it, learn how it works, and decide if they want to use it for their real work. It's like a "try before you buy" opportunity for businesses to make sure they're making the right choice.

Note- As trials are limited to 30 days, it's advisable to wait until you have sufficient time to dedicate to working within the trial.

Prerequisites: To set up a Dynamics 365 trial, you'll require a Microsoft account. If you don't have an existing Microsoft account or wish to create a new one, you can begin the process on the official Microsoft website.

Explore various modules available in the free trial version. You can access all of them right here
URL - https://trials.dynamics.com/

Creating a Trial Instance in Dynamics 365

Follow these detailed steps to set up a trial instance in Dynamics 365:
Step 1: Start by opening your web browser and click on the following link to access the Dynamics 365 Marketing Home Page: Link here This link will take you to the main page where you can initiate the trial setup process.

Step 2: On the Dynamics 365 Trial Home Page, locate and click on the "Try for free" option under Sales Module. This will be a clickable button or link that's designed to start the trial registration process.
Step 3: You'll be prompted to provide your email address. It's important to use your Microsoft account ID for this step. Note that non-Microsoft email accounts won't be accepted for the trial. Once you've entered your Microsoft account email, click on the "Start your free trial" button to proceed.

Step 4: After clicking the "Start your free trial" button, you'll be asked to enter the password associated with your Microsoft account. This is a security measure to ensure the authenticity of your request. Once you've entered your password, click on the "Sign in" button. After signing in, you might need to click "Submit" to confirm your information.

Step 5: Now it's time to add your personal information. Fill out the form with the required details about yourself. This information might include your name, contact information, and any other necessary details. Once you've completed the form, click "Next" to proceed.

Step 6: After submitting the form, you'll be directed to a new page. Here, you'll receive a confirmation that Microsoft is in the process of creating your trial instance. This might take a moment. 

Step 7: Once the trial instance is fully created, you'll see an option to "Launch Trial." Click on this option to access your newly created Dynamics 365 Sales trial instance.


Step 8: Congratulations! Your Dynamics 365 Sales trial instance is now accessible and ready for use. You can begin exploring the features and functionalities offered by Dynamics 365 to support your work and business needs.


By following these detailed steps, you'll successfully create a trial instance of Dynamics 365 Sales and be on your way to utilizing its capabilities for your tasks and projects.

Go to the Power Platform Admin Center at https://admin.powerplatform.microsoft.com/home 
Click on "Environments" to view the Trial Environments and add a new one by selecting the "Add new" button.

Followers

Power Dynamix YouTube Videos