Introduction: This blog explains how to migrate data for Many to Many or N:N relationship records. Scenario: Client always demand configuration records to be migrated from Test Env to a Production Environment.We can migrate data for Entity records and Entities with 1:N relationships records however we cannot directly migrate data for N:N relationship( intermediate entity) which is not exposed in D365 PSA. This can be achieved by using XRM Tool Box plugin – Manage NN relationships. Prerequistive: · XRM Tool Box with “Manage NN relationships” plugin installed. · Both entities having alternate key with data – This is required as a cleaner approach. Below steps explains how to achieve requirement. Steps of Implementation: 1. Open “Manage NN relationships” plugin in XRM tool box with Source Organization as connected. 2. Click Load Metadata button and then select First Entity with Specific attribute as alternate Key and same for Second Entity as shown below. 3. Click button Export button and save file. 4. Open exported file Column A is OrgUnitID and Column B is PriceLevelID data. 5. Change connection to target organization of Manage NN relationship plugin in XRM toolbox and then follow the step 1 and 2. 6. Click Import button and select the file exported in step 3. 7. Data migrated is been tracked in log section of plugin. Conclusion: N:N relationship or Many to Many relationship entity records cannot be migrated from D365 PSA as they are not been exposed however this can be achieved by using third party tool like XRM Tool Box – “Manage NN relationship”.  

Overview: Often while working on PS, I was struggling to  get the Chargeability View right. The main reason is not having the right Price List setup at the right places. There are 4 important places where the Price Lists need to be setup properly. Product Catalog with Role Prices having Org Unit A Account having corresponding Sales Price List and the same Sales Price List under it’s Project Price Lists grid. Opportunity having Org Unit A as Contracting Unit and Product Price list having Sales Price List for Org Unit A selected. Quote derived from the Opportunity having the same Account, Opportunity, Contracting unit and Product Price List selected. Organization Unit: For each Organization Unit you add to PSA, make sure you’ve added a Cost Price list to the Organization Unit as well as a Sales Price list exists for the same. Make sure Organization Units on the Role Prices are selected correctly on both the Sales and Cost Price Lists Sales Price List on Account and Opportunity: Account and Opportunity too should have the same Sales Price list whose Cost Price list is associated with the Organization Unit of the Account’s and Opportunity’s Organization Unit. Make sure you’ve correct Organization Unit and Product Price List as a Sales Price List for that Org Unit selected on the Opportunity form. Chargeability View on Quote Lines: Once everything flows from Account to Opportunity to Quote and to Quote Lines, you can see that your Chargeability View pops-up properly. Hope this helps you derive correct Chargeability View without hassle.

Introduction  In earlier version of dynamics CRM, there were no way to define dependencies of web resource.  Due to this, it is possible that someone delete/remove WebResource from solution and this may create an instability in behavior of CRM functionality. But now in dynamics  365 version 9.0. It has ability to define  dependencies of WebResource. Description: Let’s consider below example. I have 3 web resources- new_test.js new_test2js new_test3.js Here new_test3.js is dependent on new_test.js and new_test2.js. in that case we need to define dependencies. Once dependencies are defined it will not allow to delete WebResource. Add Dependencies: If you want to add dependencies in WebResource, you can follow below steps Open WebResource which is dependent on other WebResource Select dependencies tab as shown and click on add Select WebResources that are required to present Save and publish WebResource. If anyone accidentally tries to delete WebResource. He will receive alert message. It will list down where this file is needed Conclusion: By following these steps, you can create WebResource and define dependency of WebResources.

Introduction: In Many scenario vendors send one invoice for multiple purchase order. In below article explain how to create single invoice for multiple purchase order. Steps: Create Two Purchase orders for same vendor. PO 1st : Quantity-50, price-25 PO 2nd: Quantity- 15, Price-20 Select PO’s for which you want to create invoice Click on Invoice button in Invoice tab. Enter the same Invoice number for two Purchase orders. Click on Consolidate Invoice button and select Invoice account in summary update field. And click on consolidate. One Invoice will create for two Purchase order Click on Post button to post the Invoice. Click on Invoice journal button to check invoice line for multiple PO Click on line to check invoice lines for multiple PO Conclusion: This functionality is useful for create single invoice from multiple Purchase orders.

Introduction: People using ADX Portal often face the issue of clearing cache due to which changes aren’t being reflected on the frontend. In this blog we will see how a user can manually clear cache in ADX Portals to reflect changes made to Portals through CRM. Pre-Requisites: ADX Portals CRM Environment Scenario: One scenario mostly faced is that notes added in CRM in the activity section of a particular case aren’t appearing in the notes section on the case entity form in portals. The problem can be resolved by clearing the cache of the portals which will help to reflect the changes made to portals via CRM. We will see below how we can resolve the issue by using manual cache clearing technique. Process: Step 1: User while adding notes in CRM will have to add the prefix as *WEB* to the note. For eg. “*WEB*This note states the resolution of the case Step 2: The user will have to save the following ” javascript:var url=document.location.protocol+’//’+document.location.host+(document.location.host.indexOf(“demo.adxstudio.com”)!=-1?document.location.pathname.split(“/”).slice(0, 3).join(“/”):””)+’/Cache.axd?Message=InvalidateAll&d=’+(new Date()).valueOf();var req=new XMLHttpRequest();req.open(‘GET’,url,false);req.send(null);window.location.reload(true);”  as a Bookmark in the URL section in the Browser. For Chrome Browser: In Bookmarks section of chrome we will add a new bookmark as shown below: Select  “Add new bookmark” to add a new bookmark in the dropdown options Name the bookmark as “Cache Invalidate” and add the following to the URL   “javascript:var url=document.location.protocol+’//’+document.location.host+(document.location.host.indexOf(“demo.adxstudio.com”)!=-1?document.location.pathname.split(“/”).slice(0, 3).join(“/”):””)+’/Cache.axd?Message=InvalidateAll&d=’+(new Date()).valueOf();var req=new XMLHttpRequest();req.open(‘GET’,url,false);req.send(null);window.location.reload(true);”. Click on save once done. Enable “Show bookmark bar” which will display the added bookmark to the chrome ribbon. Step3: On opening the case page click on the saved Bookmark “Cache Invalidate” on the bookmark bar which will make the note visible in the note section. Conclusion: In this way we can manually clear the cache which will reflect the newly made changes to ADX Portals.  

Introduction: Customization of any particular form or table is done by creating extensions. Any modifications or to add some fields to an original object can be done by creating extensions. At run time all these extensions run as single object. In this blog we demonstrate how to add fields to an existing form. Consider the form CustTable and add two fields in the form. Passport Number Age Step 1: From Application explorer open DirPerson Table –> right click and click on create extension Step 2: Open the table designer and expand the fields. Add the two fields and set the appropriate properties. Step 3: From Application explorer open CustTable Form –>right click and click on create extension Step 4: Open the form designer of CustTable. Expand the deign portion until you reach the control, where you want to add required field. for example I want to add New fields in Person Detail section. Step 5: Open the data sourceà go to fields and drag and drop the newly created field. Save the changes and build the project. Step 6: This adds the fields to the form.  

Overview: After much wait, the new Email feature in the Unified Interface is finally here. So this blog is about what all the new Email functionality can do in the Unified Interface. This feature is only for the Unified Interface. Now, you can see the Email button appearing on the ribbon. In the To field, you can select the record type in more intuitive way without having to load the Lookup view. Rich Text Editing: Now, the new Unified Interface offers Rich Text Editing capabilities wherein you can add new media to your email body. HTML Preview: Even you get to see the HTML preview of your email Preview of the Email You’d definitely want to see what goes out before sending the email out. You can also preview the final email before sending the same. Email: And this is how it looks when received by the recipient Hope this helps to a great start in email editing in D365!

Introduction: Reports are used to see summary of data.  We also set parameter to filter data but at times we don’t want to filter using a parameter and keep it as blank. By default, parameter values are always mandatory in D365 Finance and Operations, Enterprise Edition. In this blog article, we will see how we set property to allow null values to a parameter in SSRS Report. Steps: Go to Report -> Parameters. Select the Parameter which you don’t want to be mandatory. Go to Properties -> Nullable. Set the value to True. This will allow you to pass null value. This is how you can make the report parameter as optional.

Introduction: This blog consists of information on how you can find the triggering parameter of the Workflow. Scenario: There are many workflows on update of a record and which workflow is triggering for which fields and on which fields the workflow is dependent on. It may be handy to identify which fields are being used to trigger workflows. You would open each workflow and check or you could click field in every entity and Check Dependencies. But there is much easier way for it. Solution: We can make use of Advance Find on the Process Entity. There are some fields like 1) Trigger On Update Attribute List 2)Trigger On Create 3) Trigger On Delete 4) Is Child Process This fields can be useful in many ways. Trigger On Update Attribute List has a field list separated by comma. This are the fields on which the workflow triggers.

Introduction: Dynamics 365 for Retail Provides Modern POS functionality (MPOS). It supports online as well as offline mode. The blog describes the configuration and Installation of MPOS step by step. Steps: Step 1: Go to Retail -> Channels -> Retail Stores -> All Retail Stores Select the Store for which you want to configure MPOS. In my case I have selected the warehouse. Step 2: On right hand side Go to registers and select which register you want for that particular store. Double click on the register Step 3: Under General Fast Tab, Enable Support Offline and Double click on the Device Please Note: If Device is not set for the register of the store. Go to Devices and assign a device of type Retail Modern POS to the register. Step 4: Click on Download and select the Configuration file Step 5: When the download starts click on save or the browser will automatically download it. Step 6: Again Go to Download and now select the Retail Modern POS Step 7: Once the download starts click on Save and then click on Run. This completes the installation of Modern POS