Introduction: After the release of Microsoft Dynamics CRM update 1, Microsoft has removed the mobile version of form and made actual form available for the Mobile/Tablet. But, since few scripts do not work on mobile/Tablet, and work fine on the Browser, Microsoft has released the guide line that should be followed while writing the scripts. Kindly refer the below link for further details on the guide lines provide by Microsoft. https://msdn.microsoft.com/en-in/library/dn481572.aspx There are scenarios where scripts break and we are not able to debug them on phone/Tablet. Which leads to no proper error tracing by the developers. Description: The script which worked perfectly fine on the Web Browser, had issues on phone/Tablet. These scripts sometimes have more than thousand lines of code and we struggle to find what exactly is causing it to fail. Microsoft, for the same reason has now come up with a solution to debug these scripts. Follow the below steps in order to debug: Step: 1 While writing script makes sure to include the ‘debugger;’ tag in the beginning of the function or where you want to debug the code. Step: 2 Create a URL which works same as that of tablet. https://<CRMURL>/nga/main.htm?org=<OrgUniqueName>&server=<CRMURL> Step: 3: For e.g. the organization URL will look like below. Unique name of the org can be obtained from Settings -> customization -> developer resource -> unique name Before opening the above mentioned URL make sure you are already logged in the web browser else the link will not work. Step 4: You will receive the below message whenever there is a change in the customization. Makes sure to download the latest changes, it will take few seconds.   Step: 5 Once the download is completed you can test your script by pressing F12 button, in our case I have registered the script on change of Phone field as you can see below. As soon as the value of Phone field changes it takes me to the debugger line. (PFB the screen shot for the same) Using this approach, you can debug the script on the desktop using the tablet version of CRM.   Conclusion: We can debug the mobile version of script on the web browser by the steps provided. Which will allow better debugging than the manual one that the legacy system had.  

What is Interactive Service Hub? Interactive Service Dashboard is a single place where Customer Service Manager/Customer Service Representative can perform all customer service related activities. This feature is introduced in CRM Online 2016 Update and is available on CRM 2016 On Premise as well. What is not supported by Interactive Service Hub? This feature is available only on Web Browser and is not available on clients like CRM for Outlook, CRM for Phones and CRM for Tablets. Right to Left (RTL) languages are not supported. e.g. Hebrew and Arabic Third party accessibility aids such as Screen readers are not supported. Keyboard navigation is also not possible in Interactive Service Dashboard. How to access Interactive Service Hub? Below are the 3 ways in which you can access Interactive Service Hub: From CRM Notifications ribbon   From Settings -> Interactive Service Hub   From putting URL in browser CRM Online Environments: https://<CRM Server>.crm#.dynamics.com/engagementhub.aspx CRM On Premise Environments: <your CRM Server>/<orgname>/engagementhub.aspx Internet Facing Deployed (IFD) Environments: https://< hostname[:port]>/engagementhub.apsx. Manage Different Record Types Interactive Service Hub can be enabled for any entity. By default, it is enabled for below entities: Accounts Contacts Cases Activities: Email, Task, Appointment, Phone Call, Social Activity Queue Items Dashboards Social Profiles Entities which are enabled for mobile are also available for use in the interactive service hub, but these records are read-only. Interactive Service Hub Navigation Menu Note: Navigation bar of Interactive Service Hub is different than that of CRM. In Interactive Service Hub navigation, only those entities are shown that are enabled for Interactive Experience. Like CRM Navigation, we can go to any interactive experience enabled entity from top Menu as shown in below screenshot. When you open any record in Interactive Service Hub, you can navigate between records of the view (from where record is opened) using arrow Keys. You can also see recent records similar to CRM as shown in below screenshot Or You can create records using ‘+’ sign in navigation bar. You can use Search option to search records in Interactive Experience Enabled entities. Understand new form layouts in Interactive Service Hub Business Processes In interactive service hub, business processes are shown as a process bar on forms on top. By default, the process bar is collapsed and when user clicks on any state, its fields are popup as fly out. Default collapsed view: When user clicks on stage: Entity Forms Unlike CRM forms, in interactive service hub, tabs on forms are placed horizontally as shown in below screenshot. Entity Card For interactive service hub, new form type is introduced as Card. Card is shown as a tile in interactive service hub with most important details of the record in shorter area. Below screenshot shows how cards are shown in interactive service hub. Timeline In interactive service hub, on case record, the timeline section is added to help users in tracking all case history right within the same page without navigating to multiple places. You can create any new activity, search or filter activities in Timeline section. You can also perform quick actions on the activities right from Timeline section. You can navigate to respective activity by clicking title of an activity. Related section on entity record We can see list of related records in same page of entity record form. For cases, user can directly see knowledge articles. Dashboards My knowledge dashboard This dashboard is designed to provide an overview of knowledge base articles, e.g. number of knowledge articles and their status, etc. This helps knowledge manager in knowing about expiry month of articles, number of articles to review, etc. Stream shows data from views/ queues. In knowledge dashboard, the stream shows the active articles assigned to the author. Charts provide a count of relevant records in the streams, such as articles by status reason, articles by owner, etc. Charts can be drilled down to see details. Tiles give authors numerical values to get an idea about the status of knowledge data. We can perform actions directly from dashboards without opening record. e.g. if we want to close a case without, we can directly do so from dashboard as shown in below screenshot: Customize Interactive Service Hub Forms Supported Entities Below are the only out of box entities which are allowed for interactive service hub and are by default enabled: Account Contact Case Out-of-the-box activities (phone, task, email, appointment, and social activity) Social Profile Queue Item Knowledge Article Custom entities can be enabled for interactive experience. Entity Form Types Main – Interactive experience Only used in interactive service hub. This is the main form to which is shown when user access any entity record in interactive service hub. Card Form Only used in interactive service hub. This is the form which is shown in dashboard stream areas. Quick Create This form is shared between Dynamics CRM and Interactive Service Hub. This form is used to quickly add records and is rendered vertically at the right side of the screen in interactive service hub. Quick View This form is shared between Dynamics CRM and Interactive Service Hub. This form is used to show related information of any lookup field. Reference Link How to create/design interactive forms: https://technet.microsoft.com/library/b6df6d11-9272-4c68-b516-e12c6e701622.aspx How to customize interactive service hub: https://technet.microsoft.com/library/d1446a95-14bf-4b15-a905-72fce07f4c76.aspx Work with interactive service hub form components: https://technet.microsoft.com/en-us/library/mt622060.aspx  

Consider a scenario where we want the Invoice generated in Microsoft Dynamics CRM to be saved in an ERP. In this article, we will migrate the invoice that is generated in CRM to Dynamics NAV using TIBCO Cloud Integration as Integration Tool. Prerequisite: CRM Online environment Dynamics NAV TIBCO Cloud Integration subscription TIBCO Cloud Integration On-Premise Agent on the server where Dynamics NAV is installed Step 1: Login to TIBCO Cloud Integration Login to TIBCO Cloud Integration (https://online.scribesoft.com/) in the server where Dynamics NAV is installed Go to Agents and create Agent from NEW option Install On-Premise Agent and copy the Agent key as well After installation, you can provide the name for the agent Step 2: Creation of Source and Target connection. Creating a new connection for CRM environment: Select ‘Microsoft Dynamics CRM’ as the Type. Provide the connection details and select ‘Cloud Agent’ for CRM Online environment as shown in screenshot below. Fig. Connection for Dynamics CRM   Creating a connection for Dynamics NAV: Select Microsoft Dynamics NAV as the Type. Provide the connection details and select the On-Premise Agent which is installed on the server where Dynamics NAV is installed. Refer below screenshot for the same. Fig. Connection for Dynamics NAV   Step 3: Creating solutions for maps Create a new solution. Select the On-Premise Agent. Create Advanced Map.Note: There will be two Advanced Maps in the solution. One for ‘Account’ entity migration from CRM to NAV and one for ‘Invoice’ entity migration from CRM to NAV. In the Map for Account migration: Select source connection as the CRM connection In the Query block select ‘Account’ entity Select the target connection as the Dynamics NAV connection In the Create block of the target connection select ‘NAVCustomer’ entity In ‘Create’ block map the required fields. Also we need to use the ‘Update’ block to update the ‘No’ field generated for a Customer in NAV to the ‘accountnumber’ field in CRM. We use the ‘accountid’ field as the matching criteria in the update block. Fig. TIBCO Cloud Integration Map for Account migration   In the Map for Invoice Migration: Select source connection as the CRM connection Select ‘Invoice’ entity in the query block Add invoicedetail as ‘Related entity’ in the Query block Select the target connection as Dynamics NAV connection The flow for creating the Invoice and its related invoice product is as follows: Fig. TIBCO Cloud Integration Map for Invoice migration Step 1: Lookup on account entity in the source and fetch its accountnumber field (which will contain the No that we have updated in the Account migration map). Step 2: Lookup on ‘NAVCustomer’ entity by using the accountnumber fetched in Step 1 as matching criteria and fetch its Name. Step 3: Use ‘Create’ block to create the Invoice entity in NAV. Select ‘NAVInvoice’ entity in the create block. Map the fields required. Fig. Mapping for Create block in NAVInvoice   Step 4: Use ‘For each child’ block for fetching the products present on that particular invoice. Step 5: Use create block in the ‘for each child’ block and select ‘NAVInvoiceSalesLines’ entity. Fig. Mapping for Create block in NAVInvoiceSalesLines   Step 5:Execution of maps for account and invoice entities. Account is updated in CRM. Fig. Before execution of CRM account Fig. After execution the AccountNumber is populated with the No that is generated in NAV   Customer is created in NAV. Fig. Customer in Dynamics NAV   Create an invoice with this customer in CRM and Run the Map. Fig. Invoice in Dynamics NAV   An invoice is created with that customer in NAV.  

Prerequisite: Power BI Desktop Tool, Power BI Online Service Purpose of the setup: Purpose of this blog is to demonstrate Row Level Security (RLS) using Power BI Procedure: To demonstrate this, we have created a Power BI Desktop file and published it to Power BI Online account. Before starting, let us assume a scenario where there is a Sales Organization. A Sales organization uses CRM data. They need to provide Sales data by Role to different person as per their job profile or control. CEO of a Sales organization can view data for all the opportunities. Sales Manager can view only his related sales data i.e. opportunities created by the Sales Person under his team. Sales Person can view only his sales opportunities. Fig 1: Scenario   This can be achieved using RLS in Power BI. Steps Here we have created a Dashboard with sample data for a Sales Organization that deals with Opportunity data from CRM. Fig 2: CEO Dashboard   This is the Opportunity dashboard that shows the complete CRM Opportunity data of the organization. Now if the CEO wants to restrict the Sales Manager and Sales Person to view only at their level i.e. the Sales Manager can view data under his team and a Sales Person can view only his data as an owner. For achieving this the CEO can share the dashboard to the person and then can assign the role. Step 1: Select the dataset from which the row level security has to be applied. There is a new option called SECURITY, which we find once we click on the ellipses (…) next to the dataset. Fig 2: Security Option   Step 2: Now click on Create New Role then add the email address of the person (which he uses as login id for his Power BI account) and then click on Add. Fig 3: Adding Members to RLS   Step 3: After adding the members click on Rules to provide the filtering of data based on DAX filters. In Rules we have to select the table(s) on which we have to apply filter and then write the DAX Function in the DAX Input box. Finally click on SAVE. Fig 4:  Rules Option   Step 4: Now we are done with RLS in Power BI, to view the result we can go to the person’s Power BI account and find the result. Note: It may happen that the result is not visible immediately. So for that we can refresh the Power BI dashboard once. In this case the dashboard has been already shared with the Sales Manager who according to the scenario is the Sales person in our case. Fig 5: Sales Manager Level Dashboard   Similarly, CEO can apply RLS for a sales person to restrict to his data on dashboard. Fig 6: Sales Person Level Dashboard   This is how RLS is achieved using Power BI. Since, this is in Preview there are few limitations too. Limitation: You can define RLS only on the datasets created using Power BI Desktop client If you make a change to your PBIX file, and republish to the service, you will need to re-create RLS Defining RLS in a group workspace is not supported You cannot add security groups or distribution lists to the member list Q&A and Cortana is not supported with RLS  

Introduction We frequently come across requirements where customers use Dynamics CRM and Salesforce CRM and want to synchronize data between both the systems. We generally have requirements where data should flow back and forth from Dynamics CRM and Salesforce CRM. In this blog, I have focused on one way real time integration of Case entity from Dynamics CRM → Salesforce CRM. Requirements We have total 4 environments as per below: Dynamics CRM Development Dynamics CRM Production Salesforce CRM Sandbox Salesforce CRM Production The requirement is to perform development on development environment and then deploy the changes on production environment. There should be no code changes done on production environment and hence the solution should be configurable. Only below basic fields of Case entities should be mapped i.e. transferred from CRM Online à Case Title (Text field) Customer (Lookup of Account field) Contact (Lookup of Contact field) Description (Multiple line of Text field) Origin (Option Set) Salesforce Id (Text field – custom field to track GUID of case record created in Salesforce) Basics of Salesforce API Salesforce has list of APIs (https://developer.salesforce.com/page/Salesforce_APIs) from which we have used Partner WSDL (SOAP API). To login to Salesforce using APIs, we need to have below 3 details: User Id Password Security Token Unlike Dynamics CRM, Salesforce API uses 2 separate URLs based on environment type i.e. Sandbox/Production. Sandbox Environment uses Production Environment uses Implementation Approach To ensure no code changes on production, we have used configuration entity which will keep below configuration details: Salesforce User Id Salesforce Password Salesforce Security Token Salesforce environment Type We have used Partner WSDL to communicate between Salesforce environment and CRM Online environment. Hence based on Salesforce Environment Type, we are using login URLs. To achieve this, we have done a trick (explained below in Implementation Steps section). On create/update of Cases in CRM Online, we have written a plugin that sends data to Salesforce environment. Implementation Steps Note: I have used a separate class file that keeps all constant values. Hence whenever you find any code in all capitals, kindly replace constant values as per your requirements. Generate Partner WSDL for Salesforce environment (https://developer.salesforce.com/docs/atlas.en-us.api.meta/api/sforce_api_quickstart_steps_generate_wsdl.htm) Create Configuration entity in CRM with below fields: Key (text) Value (text) Create a plugin class and perform below operations in the plugin. Add web reference using downloaded Partner WSDL (https://msdn.microsoft.com/en-us/library/bb628649(v=vs.100).aspx). After adding web reference, you will see reference in Solution explorer as per below. Expand Reference.map and open Reference.cs class. Locate SforceService() method and create a copy of the same with one string parameter as per below and save the file. In plugin class, fetch configuration details from Configuration entity. It should contain 4 records. Based on the environment type, pass appropriate URL to the service to authenticate with Salesforce environment. private void ConnectToSalesforce() { LoginResult currentLoginResult = null; switch (this.dctConfigurations[CodeConfiguration.ConfigurationKeys.SalesforceEnvironmentType.ToString()]) { case CodeConfiguration.SALESFORCE_SANDBOX_ENVIRONMENT_TYPE: this.sfdcBinding = new SforceService(CodeConfiguration.SALESFORCE_SANDBOX_WEBSERVICE_URL); break; case CodeConfiguration.SALESFORCE_PRODUCTION_ENVIRONMENT_TYPE: this.sfdcBinding = new SforceService(CodeConfiguration.SALESFORCE_PRODUCTION_WEBSERVICE_URL); break; default: throw new InvalidPluginExecutionException(CodeConfiguration.ERROR_MESSAGE_CONFIGURATION_NOT_FOUND); } currentLoginResult = this.sfdcBinding.login(this.dctConfigurations[CodeConfiguration.ConfigurationKeys.SalesforceUsername.ToString()], this.dctConfigurations[CodeConfiguration.ConfigurationKeys.SalesforcePassword.ToString()] + this.dctConfigurations[CodeConfiguration.ConfigurationKeys.SalesforceSecurityToken.ToString()]); this.sfdcBinding.Url = currentLoginResult.serverUrl; this.sfdcBinding.SessionHeaderValue = new SessionHeader(); this.sfdcBinding.SessionHeaderValue.sessionId = currentLoginResult.sessionId; } Once authenticated, use the session id to perform CRUD operations. Below is a sample code. Create an object of case record to be created in Salesforce sObject caseRecord = new sObject(); caseRecord.type = Case_Salesforce.LOGICAL_NAME; Create objects of attributes of the case record XmlElement[] caseFields = new XmlElement[10]; XmlDocument doc = new XmlDocument(); caseFields[counter] = doc.CreateElement(Case_Salesforce.ATTR_CASESUBJECT); caseFields[counter++].InnerText =”Any value”; caseFields[counter] = doc.CreateElement(Case_Salesforce.ATTR_CONTACT); caseFields[counter++].InnerText =”Salesforce Guid of Contact record”; caseFields[counter] = doc.CreateElement(Case_Salesforce.ATTR_ORIGIN); caseFields[counter++].InnerText =”text value of an option from picklist”; Add attributes to an object of case record caseRecord.Any = caseFields; sObject[] caseList = new sObject[1]; caseList[0] = caseRecord; Create record in Salesforce SaveResult[] results = null; results = this.sfdcBinding.create(caseList); for (int j = 0; j < results.Length; j++) { if (results[j].success) { Entity oCase = new Entity(Case_CRM.LOGICAL_NAME, this.currentEntity.Id); oCase[Case_CRM.ATTR_SALESFORCEID] = results[j].id; this.service.Update(oCase); LogIntegrationDetails(“Record Id: ” + this.currentEntity.Id.ToString(), null, (int)IntegrationLog.Status.Success); } else { for (int k = 0; k < results[j].errors.Count(); k++) { Error err = results[j].errors[k]; } } } Key Takeaways From Dynamics CRM → Salesforce, real time integration is possible using CRM plugins and Salesforce APIs. Salesforce uses different authentication URLs for different type of environments. We have handled this scenario by modifying Reference.cs class file. Configuration entity is used to make the code configurable. We are storing back GUID of case record created in Salesforce which will be used in case of update plugin.  

In this article, we are going to see how ClickDimensions enables Marketers to create interactive automations based on prospects or user behaviours which will help to design unique paths for participants to follow as they interact with our messaging it also helps to create Lead-nurture marketing campaigns, Sales engagement campaigns, promotional or event campaigns, new customer on boarding and retention campaigns, and many more. Campaign Automations allows to set up a dynamic paths for a contact or lead to follow based on actions taken by that contact or lead. For example, if the contact fills out a form on your website than you can send them an email then wait to see if they click on Link A or Link B. If they click on Link A send them Email A, but if they click on Link B send them Email B. Navigate to Marketing > Marketing Automation > Campaign Automation.   Choose New   This window will open where you will need to fill in a few fields.   Name [Required]: This is the name of the record as you will see it in CRM. Campaign: You may choose a CRM Campaign here if desired. This will associate this record to that CRM Campaign. Which will help us to track the ROI (Return on Investment) Completed Instances: Number of instances of Contacts and Leads who have finished running through this Campaign Automation. This is a read only field that will automatically be filled in once the Campaign Automation has been published. Owner [Required]: You will be the owner but you may change this if you’d like. Status [Read only]: This will change when the Campaign Automation is published, paused, or stopped from within the builder window.   After filling out any required fields, click Save.   Then click Open Builder.   You will now see the canvas where you will build your campaign automations.   On the right side there are Triggers and Series. Click and drag these onto the canvas.   Connect them together to make a path by clicking on the green dot on the right side of the trigger and dragging to the green dot on the left side of the series.   You can create a Decision Node by connecting the trigger to multiple Series. This will allow you to choose a path based on something in the previous trigger, values of form fields for example.   Let’s go through each pieces of the Campaign Automation builder Triggers These are the different ways contacts/leads can be added to the Campaign Automation: Submitted For Email Interaction Added to List Manual Add   Submitted Form   The Submitted Form trigger may be used as an Entry Point Trigger or an Internal Trigger. If the trigger is an entry point and a contact or lead has filled out the selected form, the Campaign Automation will begin. Add a Submitted Form trigger to the canvas and click on the node. You will see the right panel change to show the properties.   Display Name (Required): Once you select a form this will change automatically to the name of that form, however you may change it to whatever you would like. Select form (Required): Choose an already created form. Here we have selected Service quick start form Campaign: If you set a campaign on the Campaign Automation record this field will be populated with that campaign. You can also choose something different. This will set the Campaign field on the Posted Form record. Note: A note is an optional field for any details that need to be written about the trigger. Email Interaction   The Email Interaction trigger may be used as an Entry Point Trigger or an Internal Trigger. If the trigger is an entry point an Email Send will be selected and then sent when the Campaign Automation is published. It will then check to see which contacts click or open that email. If the trigger is an internal trigger it will check for clicks or opens on any selected email(s) sent in the preceding series via Send Email actions. Add an Email Interaction trigger to the canvas and click on the node. You will see the right panel change to show the properties.   Display Name (Required): Type a Display Name to show on the canvas. Select Email Send (Required): Choose a draft Email Send. Before you publish this Campaign Automation make sure to add recipients to your Email Send. Note: A note is an optional field for any details that need to be written about the trigger. Select which interaction to monitor: Email Clicked: If checked, you will be given the option to choose which links to look for. Email Opened (without click): Check this if you want to do something if someone opens the email but never clicks Selecting an interaction If Email Clicked is checked, a link to select which links will appear.   Click this and a window will open with the email chosen in the Email Send lookup.   As you can see in the above figure the email has got all together 9 links. Select one link, several links, or all links. If any one of the links selected is clicked, this trigger will be activated. If Email Opened (without click) is ALSO checked, you may select the amount of time to wait to see if the contact/lead clicked any of the selected links before checking to see if the contact/lead at least opened the email. If you do not select a time it will just wait to see if the recipient interacted in any way.   If Email Opened (without click) is the only one checked it will just wait to see if the email was opened. Upon clicking in the canvas, you changes will be saved. To edit the node’s properties, simply click on the node and make any necessary changes. Added to List   The Added to List trigger may be used as an Entry Point Trigger or an Internal Trigger. If this trigger is an entry point, any time a contact or lead is added to the specified marketing list, that contact/lead will enter the automation. To … Continue reading ClickDimensions Campaign Automation →

In this article we are going to see how to send a specific email to a customer depending on how they answer a certain Form Field. This is something which can be easily accomplished with a workflow. In our example, we have created a form asking people which EazyAPP product they are interested in learning about: Gravity forms, Client Portal or Marketing with ClickDimensions. We want customers to be sent a specific email with regards to the specific product they requested for.   The form field we created is called Field Interest, and we made it a list with the three options.   We then created three separate email templates that we would like to send customers based on how they answered our field. Here is the email template for customers interested in Gravity Forms:   Now we can set up our workflow that allows specific emails to be sent based on how our Field Interest form field was answered by each customer. We set up this workflow to run on Posted Fields, set the scope to organization and set it to run when the record is created.   For our first step, we added a Check Condition that asks if the posted field is Field Interest and the posted form is our ClickDimensions Product Interest Form.   Then we asked if the value of that field equals Surveys. Remember, the value is how the data is stored in CRM, which may be different than the label that appears on your form.   When the value is Surveys, we added a Create Record step and chose “Send ClickDimensions Email.”   We then opened up the Set Properties and uploaded our survey email template. We also added the recipient as the Contact associated with the posted form.   We then repeated these last two steps for our Client Portal and Marketing (ClickDimensions) options. Our final workflow looks like this:   Now, customers who fill out our form will receive an email specifically about the product they were interested in.  

Prerequisite: Power BI Desktop tool, SQL Server Database Purpose of the setup: Purpose of this blog is to demonstrate connecting SQL as a data source to Power BI Desktop Tool using Direct Query Mode. Procedure: To get this done we have created a Power BI Desktop Tool file with source data of SQL file connected using Direct Query mode. (a)   (b) Fig 1: Power BI Desktop Tool file using Direct Query Mode As we know, previously there were many restriction in using Direct Query Mode like we could not view the relationship, cannot create calculated columns and measures etc. But now, there are many updates in Direct Query mode few of which will be demonstrated below. Ability to create calculated columns in Direct Query. Ability to create measures in Direct Query. Ability to change the datatype when connected to Direct Query. Ability to assume Referential Integrity on relationships in Direct Query Ability to create calculated columns in Direct Query Now we can create calculated column in Direct Query using DAX function. Right click on the table area and select calculated column then write the required DAX query to get the column. Below is an example where we have created a calculated column in Direct Query. Fig 2: Create New Column option in Direct Query Mode   Fig 3: Created calculated column in Direct Query Mode   Ability to create measures in Direct Query Now we can create measures in Direct Query using DAX function. Right click on the table area and select measures then write the required DAX query to get the column. Below is an example where we have created a measure in Direct Query. Fig 4: Create new Measure option in Direct Query Mode   Fig 5: Created Measured in Direct Query Mode   Ability to change the datatype when connected to Direct Query Now we can also change the datatype in Direct Query. Fig 6: Change Datatype option in Direct Query Mode   Ability to assume Referential Integrity on relationships in Direct Query A new setting has been added to the Edit Relationship dialog: a checkbox to “Assume Referential Integrity”. This setting is applied to imported and created data model relationships. To access the setting select the Home tab -> Manage Relationships, select a relationship, and click Edit. Here we have added few tables to our Direct Query file to create some relationship between the tables and selected one relationship to get the Referential Integrity option. Fig 7: Assume Referential Integrity in Direct Query Mode   This is an advanced setting, and is only enabled when connecting to the data in Direct Query mode. It will enable more efficient queries to be generated when it is known that: The From column of the relationship is never Null/blank For every value of the From column, there is a corresponding value in the To column By setting the property in these cases, it allows more efficient queries to be sent to the backend database using INNER JOINs instead of OUTER JOINs. This will result in faster loading of dashboards for the end user.

In AX7, a new feature of Global General Journal has been released. The use of this feature is only for those companies where there are more than one legal entities in AX and the users who are doing accounting entries are same. The benefit of this feature is the user no need to switch legal entities while creating Journal Entries which can ultimately can save lot of time. The path to create global general journal is General Ledger->Journal Entries->Global General Journal. When you create a new journal, you can select the Legal entity and the journal name of that entity for which you want to create the journal entry. You can then continue to create the journal lines inside the current entity and you can directly Open the journal in the other entity if you wish to, or you can complete the entire journal entity, validate and post in the current entity and the entry will be created and posted in the destination entity.  

Introduction In earlier versions of CRM (before 2016), when a solution was exported from one environment to another, the entity and all of its assets i.e. forms, views, relationships, visualizations, attributes etc. were exported. Exporting all unrequired assets could unintentionally modify objects on Target Environment or carry unintended dependencies. In CRM 2016, solution patches can be created that contain ‘sub components’ of the entity that needs to be modified and then roll up the patches in the updated version of managed solution and export the updated version in target environment. In the section below, we look at how ‘clone to patch’ and ‘clone to solution’ features work in CRM 2016 to accomplish the above. Clone to Patch Example: Suppose there is a ‘Base Solution’, with all assets of Account and Contact entity but now we want to edit the length of field say ‘Account Number’ from 20 to 40. Step 1: Since this field is a part of ‘Base Solution’ and changing the field length is only requirement we will create a patch for the original solution. So we use ‘Clone as Patch’ option for ‘Base Solution’. Since it’s a patch, system allows only last two digits to be modified for versioning. This option creates a patch for the parent solution as shown below.     Step 2: Now in the patched solution we will only add the Account Number field of Account entity and update the field length to 40.     Step 3: When the patched solution is imported in another environment, it is applied on top of base solution and account number field is updated. Things to note when creating patches: When a patch is created at that time the parent solution is locked and can no longer be modified. Patches can be installed on another environment only If the parent solution is present in that environment. Patches should be exported as managed and should be imported on top of managed parent solution. Do not use unmanaged Patch solutions in Production environments. Patch is always created for Unmanaged Parent solutions. In the future, if any other changes are to be done in ‘Base Solution’, we can create another patch for the ‘Base Solution’ and follow the above procedure. Clone to Solution So now when we plan to have next version of solution, we use the option ‘Clone to Solution’. All related patches to the ‘Base Solution’ get rolled up in the newly created version of ‘Base Solution’ and the patches are deleted automatically.     If we want the upgraded solution to be imported on target environment, import the Upgraded Solution and then select the Parent Base Solution and choose option ‘Apply Solution Upgrade’. This option removes the previous parent solution and keeps the Upgraded new solution in the environment. Conclusion Thus with solution enhancements in CRM 2016, instead of making changes in the entire parent solution, solution patches can be created with the changed customizations and then with the help of Clone Solution option the patches gets rolled up and new version of parent solution is created.