MB-230- You are configuring a business process flow for a case entity.All cases must be flagged for review. You need to complete configuration of the business process flow. Solution: For a new action named Ready for review, disable the As a business process flow action step option. Does the solution meet the goal?

You are configuring a business process flow for a case entity.All cases must be flagged for review. You need to complete configuration of the business process flow. Solution: For a new action named Ready for review, disable the As a business process flow action step option. Does the solution meet the goal?

A. Yes 

B. No 

Answer: B

MB-230- You are configuring a business process flow for a case entity. All cases must be flagged for review. You need to complete configuration of the business process flow. Solution: Set the input parameter type as Option set for the action. Does the solution meet the goal?

You are configuring a business process flow for a case entity. All cases must be flagged for review. You need to complete configuration of the business process flow. Solution: Set the input parameter type as Option set for the action. Does the solution meet the goal?

A. Yes 

B. No 

Answer: B

MB-230 You need to consider the underlined segment to establish whether it is accurate. The status reason for a Cancelled case status will read Researching.

You need to consider the underlined segment to establish whether it is accurate. The status reason for a Cancelled case status will read Researching. 

A. No adjustment required. 

B. Waiting for details 

C. Merged 

D. On hold 

Answer: C

MB-230- You need to consider the underlined segment to establish whether it is accurate. To alter working intervals, you should configure fulfillment preferences.

You need to consider the underlined segment to establish whether it is accurate. To alter working intervals, you should configure fulfillment preferences.

A. service scheduling

B. No adjustment required.

C. resource scheduling

D. requirement groups

Ans: B. No adjustment required.

What is Entitlement in MS CRM 365

Microsoft Dynamics 365 is a comprehensive customer relationship management platform that provides businesses with a range of tools to manage their customer interactions and support operations. One of the key features of this platform is the "Entitlement" module, which enables businesses to manage and track customer support agreements in a more efficient and organized manner. In this blog post, we will take a closer look at what entitlements are, how they work, and how they can benefit businesses.

What are Entitlements in Microsoft Dynamics 365? Entitlements are customer service agreements that define the level of support a customer is entitled to receive for a specific product or service. They specify the terms and conditions of the service, such as response times, resolution times, and the types of support provided. These agreements can be used to manage and track customer support requests and ensure that customers receive the appropriate level of service based on their agreement.

How do Entitlements work in Microsoft Dynamics 365? Entitlements are created and managed in Microsoft Dynamics 365 as records that contain information about the customer, the product or service, and the terms of the agreement. When a customer support request is received, the support representative can quickly check the customer's entitlement to determine the appropriate level of support and response time. This helps to ensure that the customer receives prompt and effective support, and that their support requests are handled in a timely and organized manner.

Benefits of using Entitlements in Microsoft Dynamics 365

1. Improved customer service: By using entitlements, businesses can ensure that their customers receive the appropriate level of support based on their agreement, leading to improved customer satisfaction and loyalty.

2. Better resource utilization: Entitlements enable businesses to manage and track customer support requests more efficiently, reducing the risk of overloading support staff and improving overall resource utilization.

3. Enhanced visibility: With Microsoft Dynamics 365, businesses have a clear and centralized view of all customer support requests and entitlements, making it easier to manage and track support operations.

4. Improved reporting: Entitlements provide businesses with valuable data that can be used to analyze and improve support operations, such as response times and resolution times.

In conclusion, entitlements are a powerful tool in Microsoft Dynamics 365 that can help businesses manage and track customer support agreements in a more efficient and organized manner. By using entitlements, businesses can improve their customer service, enhance their visibility, and drive better results. If you're looking to improve your customer support operations, consider implementing entitlements in your Microsoft Dynamics 365 environment.

Convert FetchXML to QueryExpression?

FetchXML and QueryExpression are two different query languages used to retrieve data from Microsoft Dynamics CRM. FetchXML is an XML-based query language that is used to retrieve data in a more simplified way, while QueryExpression is a more powerful and complex query language that provides more options and capabilities.

In some cases, you may need to convert FetchXML to QueryExpression in order to take advantage of the additional capabilities provided by QueryExpression. Fortunately, this process can be accomplished relatively easily using the FetchXmlToQueryExpressionRequest class provided by the CRM SDK.

Here's an example of how to convert FetchXML to QueryExpression using the FetchXmlToQueryExpressionRequest class:

using Microsoft.Xrm.Sdk; using Microsoft.Xrm.Sdk.Messages; string fetchXml = "<fetch version='1.0' output-format='xml-platform' mapping='logical' distinct='false'>" + "<entity name='account'>" + "<attribute name='name'/>" + "<attribute name='address1_city'/>" + "<filter type='and'>" + "<condition attribute='address1_city' operator='eq' value='Seattle'/>" + "</filter>" + "</entity>" + "</fetch>"; FetchXmlToQueryExpressionRequest request = new FetchXmlToQueryExpressionRequest() { FetchXml = fetchXml }; FetchXmlToQueryExpressionResponse response = (FetchXmlToQueryExpressionResponse)service.Execute(request); QueryExpression query = response.Query;

In this example, a FetchXML query is created to retrieve all accounts located in Seattle. The FetchXmlToQueryExpressionRequest class is then used to convert the FetchXML query to a QueryExpression object. The resulting QueryExpression object can then be used to retrieve the data from the CRM using the RetrieveMultiple method.

It's important to keep in mind that, the conversion process may not always result in an exact match, as some FetchXML features may not have a direct equivalent in QueryExpression. Additionally, some of the complexities of FetchXML may get lost in the conversion process.

In conclusion, converting FetchXML to QueryExpression is a process that can be accomplished relatively easily using the FetchXmlToQueryExpressionRequest class provided by the CRM SDK. This process allows you to take advantage of the additional capabilities provided by QueryExpression while still using the simplicity of FetchXML. However, it's important to keep in mind that the conversion process may not always result in an exact match and some of the complexities of FetchXML may get lost in the conversion process.

Pass Parameters to Forms in MS CRM

 In Microsoft Dynamics CRM, you can pass parameters to forms by using the "OpenForm" function in JavaScript. This function allows you to open a form and pass in any number of parameters to pre-populate the fields on the form.

Here's an example of how you might use the "OpenForm" function to open a contact form and pre-populate the "Fullname" field:

var parameters = {}; parameters["fullname"] = "John Smith"; Xrm.Navigation.openForm({ entityName: "contact", useQuickCreateForm: false, parameters: parameters });

In this example, we first create an object called "parameters" and add a key-value pair to it with the key "fullname" and the value "John Smith". Next, we call the "openForm" function and pass in the entity name "contact" and the parameters object. The "useQuickCreateForm" parameter set to false, it will open the main form of the entity.

You can also pass multiple parameters by adding more key-value pairs to the "parameters" object:

var parameters = {}; parameters["fullname"] = "John Smith"; parameters["email"] = "johnsmith@example.com"; parameters["phone"] = "123-456-7890"; Xrm.Navigation.openForm({ entityName: "contact", useQuickCreateForm: false, parameters: parameters });

It's important to note that the parameter name must match the logical name of the attribute in the CRM, otherwise the parameter will not be populated.

You can also pass parameters to the forms while opening it via the command bar or ribbon buttons. You need to define the function to pass the parameters and call it on the button.

In summary, passing parameters to forms in Microsoft Dynamics CRM is a useful way to pre-populate fields on a form and save time for the user. You can use the "OpenForm" function in JavaScript and pass in any number of parameters to pre-populate the fields on the form. Additionally, you can also pass parameters via command bar or ribbon buttons by defining the function to pass the parameters and calling it on the button.