Summary A consumer appliance manufacturer was receiving warranty claims through its customer mobile app, but the replacement process still required several manual checks and handoffs. We connected the mobile warranty claim process, Dynamics 365 Customer Service, and Business Central so the claim, RMA decision, replacement order, and case history remain linked throughout the process. Table of Contents 01 Summary 02 About the Customer 03 Business Challenge 04 Solution 05 How the RMA Process Works 06 Business Impact 07 Conclusion 08 FAQs About the Customer Our customer is a consumer appliance manufacturer that sells cooking products and supports customers after purchase. When a customer faces a product issue, the service team reviews the warranty claim and decides whether a replacement or exchange is required. The company already had customer, product, and warranty information in its systems. The main challenge was moving that information from the initial claim to the replacement order without relying on repeated emails or manual data entry. Business Challenge Customers submit warranty claims through a mobile app. These claims contain important details about the customer, registered product, and reported issue. Earlier, the service team still had to review information across different records and coordinate the replacement order separately. This created a few common problems: Agents had to check customer, product registration, warranty, duplicate claim, and fraud information manually. Replacement details could be shared through emails before the order was created. The same product and shipping information could be entered more than once. The Business Central Sales Order number was not always easy to trace from the original Case. Customer Service had to spend extra time checking whether the replacement order had been created. The goal was simple: keep the warranty claim, service review, RMA details, and replacement order connected from beginning to end. Solution We connected the customer warranty journey across the mobile app, Dynamics 365 Customer Service, and Microsoft Dynamics 365 Business Central. When a customer submits a web warranty claim through the mobile app, the integration sends the claim and product details to Dynamics 365. A Case is created for the Customer Service team, giving the agent one place to review the request. During the Identification and Research stage, the agent checks the customer, product registration, warranty, duplicate claim, and potential fraud information. If a replacement or exchange is required, the agent sets RMA to Yes and records the warehouse, warranty type, shipment method, location, and products to be exchanged or added. Sample Dynamics 365 Case used to review the warranty claim and capture the RMA details. Once the required information is available, the related Sales Order is created in Business Central. The Business Central Sales Order ID is then stored back on the Dynamics 365 Case. This keeps the service request and replacement order connected, so the agent can trace the order without searching through email threads. How the RMA Process Works The connected warranty claim and RMA process from mobile submission to case closure. Step Stage What Happens 1 Warranty Claim The customer submits a web warranty claim through the mobile app. 2 Warranty Claim Integration The integration sends the customer, claim, and product information to Dynamics 365. 3 Case Creation A Dynamics 365 Case is created for the Customer Service team. 4 Identification and Research The agent checks the product registration, warranty, duplicate claim, and potential fraud information. 5 RMA Details The agent sets RMA to Yes and records the warehouse, warranty type, shipment method, location, and replacement products. 6 Business Central Order The related Sales Order is created in Business Central for replacement processing. 7 Update and Resolve The Sales Order ID is saved on the Case, and the agent resolves the Case after the required work is completed. Business Impact The connected process gives Customer Service a clearer and more consistent way to manage replacement requests. The main improvements include: Less repeated data entry: Claim and product information received through the mobile app integration is available in Dynamics 365 for the service review. Better traceability: The Business Central Sales Order ID remains linked to the original Case. Clearer agent process: Important RMA information is captured in defined fields instead of being kept only in emails. Fewer follow-ups: Agents can check the Case for the RMA and order details instead of asking another team for the order number. More consistent replacements: Warehouse, shipment, warranty, location, and product details are recorded before the Sales Order is created. Complete case history: The claim review and replacement information stay connected for future reference. Conclusion RMA automation does not need to replace the service agent’s decision. It should remove repeated entry and make the next step clear. By connecting the mobile warranty claim process, Dynamics 365 Customer Service, and Business Central, this consumer appliance manufacturer created one traceable path from a customer’s warranty claim to the related replacement order. Customer Service can work from the Case, the order can be traced through its Business Central Sales Order ID, and the complete history remains available when the Case is resolved. Frequently Asked Questions 1. What is an RMA? RMA stands for Return Merchandise Authorization. It records that a product return, replacement, or exchange has been reviewed and approved for processing. 2. How does the warranty claim enter Dynamics 365? The customer submits a web warranty claim through the mobile app. The integration sends the claim and product information to Dynamics 365, where a Case is created for Customer Service. 3. Does the automation approve every replacement automatically? No. The Customer Service agent still reviews the product registration, warranty, duplicate claim, and potential fraud information before confirming the RMA. 4. What information is captured for an approved RMA? The Case can include the warehouse, warranty type, shipment method, location, replacement products, and the related Business Central Sales Order ID. 5. Why is the Business Central Sales Order ID stored in Dynamics 365? It gives Customer Service a direct reference to the replacement order. This makes the order easier to trace from the original customer Case. Looking to … Continue reading How a U.S.-Based Consumer Appliance Manufacturer Stopped Chasing RMA (Return Merchandise Authorization) Emails with a Single Automated Workflow →

Requirement: The user will create the record from the Quick Create and on change of specific field, the record should automatically save. Whenever the record will be saved it should open the created record. In our scenario, we are going to use the Account Entity. When the user will enter the main phone data in the Account Quick Create Form, the record will automatically save and it will open the created account record. Steps: Go to Default Solution or your customization solution and Open the Quick Create Form from Account Entity 2. Click on the Form Properties to edit the form properties of Account Quick Create Form and add the script on the form. 3. Click on the +New button to add the JavasScript web resources on the form so that you can use the script function on Form Events 4. If you wanted to use an existing Web Resource then you add it or else create new by click on new 5. Create a new Script and add it on form 6. Now, we need to add the event list and bind the calling function to it. To do it click on the + New on Event Listener of Form Properties. Note: Please don’t forget to pass the execution context as the first parameter to the function. 7. We will use formContext.data.save() function to get the created record’s GUID and open entity record using that GUID. Following is code for your reference: 8. Code Explanation: a. quickCreateonSave is a function that is trigger on change of Main phone fields of Account Quick Create. b. When the function is triggered we are using formcontext.data.save to save the save so that we can get the GUID of the recently created record. c. On formcontext.data.save() we can assign two functions — on success and failure as parameter to .then() [Reference] d. On Success, the function will return the following response where you can get the entityType, entity id, and name of the record. e. After getting the entity id and entity type, we can use the open form to open the record as mentioned in the Code. 9. Publish all the customization that you have done on the Account Entity Demo: I hope it helps you guys!!

Dynamics 365 for Customer Service is the right ERP software to use if you desire to see the customer service improvement in your company. When businesses provide excellent customer support, clients not only have the best experiences, but they also stay loyal to a business. Of course, there are so many ERP solutions out there in the market. Dynamics 365 solutions are, however, the best in the world as many companies tried and tested this product and love the way it helps them to become a lot more organized. Since Microsoft owns this product, they do a lot of research to enhance this particular product. One problem people do not know how to fix is the infinite loop issue. Here are some fantastic tips to help you to surpass the problem. While using fetch xml to retrieve records more than 5000 records and if you have multiple entities involve in it. There are chances that you will get into an infinite loop even if you have less than 5000 records. Description: We have noticed that after 9.0 if you are using the old method to retrieve more that 5000 records using the fetch xml in the script it is possible that you will get the into infilter loop. This happens due to the internal multiplication of table which gives fist and last records id same in fetch XML. You need to make sure that include the header as shown in the below screen Need to make sure that you have below check condition before calling the fetch next record collection if (data[“@Microsoft.Dynamics.CRM.fetchxmlpagingcookie”] != null && data[“@Microsoft.Dynamics.CRM.morerecords”] != null && data[“@Microsoft.Dynamics.CRM.morerecords”]==true) { It has more than 1 record true only than call the next request Conclusion Hope this helps you to solve your infinite loop issue.

Customer Service is one of the essential segments of any business if they want to become successful. Every single thing about it does matter. Dynamics 365 for customer service is one of the tools that a business can use to improve brand loyalty and also to improvise the value that the companies offer to their clients. Any company that wants to improve in this segment needs to work on this thing. D365 Customer Service will set your company apart from the rest of the firms out there. This software will help you stay ahead of the customer’s expectations and to resolve their concerns a lot faster. Customers can reach out to the company a lot quicker and get resolutions for the problems they are facing at a much faster pace. Microsoft Dynamics 365 CE streamlines the way your employees communicate with customers and enhances their ability to collaborate. Problem Statement Clients implement D365 CE for all departments also need home/landing/default page for each department. This blog will help you to configure default URI for each department in D365 CE implementation for Company. Configuration Steps 1.       Open Dynamics 365 Sales app 2.       Navigate to “My Apps” in Settings group 3.       Open Manage Roles Click on ellipses(…) and pop-up open, click on Manager Role 4.       Setup App URL Enter URL Suffix e.g. SL and automatically URL is generated. 5.       Setup Roles Roles are assigned to URL, Users with specific roles can only access App. 6.       Copy URL and click Save button also share with Users for opening. Conclusion After following above configuration steps, we can share App URL with Sales Department similarly we can configure for Customer Service, Project Service, Field Service or any custom App share with the respective department. Hope this blog helps you to configure Department-wise or based on App for a group of people.

Dynamics 365 for customer service assists businesses to provide efficient and excellent customer service to improve customer service in a team. When it comes to business, every interaction that you get from your customer does matter a lot. Maximizing brand loyalty is only possible when customers get their problems or issues resolved quickly. Companies need to invest in Dynamics 365 solutions if they desire to provide the best customer service to their existing and prospective customers. It has some of the best features that can enhance your business operations. And the best part, it is quite economical than all other solutions that you now find in the market. There are so many resources that are available to make things easy for those who install and use it. We had a requirement where need to open the newly created record. Here we were using an action to create the record. Description: We had a requirement on button click contact will be created and once the record is created we need to open that record as well. Opening of the record is dependent on the user if he wants open or not. we have created a custom button and call the action which perform the operation of creation of the record. this record was created inside the action Below action was created and called on the button. 2. Output parameter was defined for the contact record that has been created inside the action 3. Once the contact record is created we set newly created contact guide as an output parameter. 4. Once that is done we got the contact id as a parameter and open it using the open form request in CRM Conclusion Hope this helps while setting output parameter value using the action.