Introduction In this blog, we will resolve “Operation has timed out” error in D365 Portals. Steps to solve this issue: Restart your portal by going to the admin center. Steps to restart the portal: Go to the Dynamics 365 Administration Center page and select the Applications tab. Select the name of the portal, and then select Manage. Click on Portal Actions –>Restart.  Click on Restart. Wait for a few minutes and go back to your portal, it should be working now. Reference: https://docs.microsoft.com/en-us/dynamics365/portals/portal-faq

Introduction: This blog details steps on how to disable most recently used items in Lookup of D365 CRM. Scenario: Enabling prefiltering on “Reported By Contact” Lookup by Service Account in Work Order Form of D365 Field Service however it shows records which are not filtered. Developers assume prefiltering is not working however it shows most recently used items also. This feature was released in version 9.1.0.3452 and it can be disabled by following the below steps. Step: Navigate to the form editor and open the lookup field’s properties dialog. The checkbox should be enabled for option “Disable most recently used items for this field” below is screenshot for reference. Below is screenshot after publishing the form and Contacts are shown as expected.   Conclusion: Hope this blog helps you resolve the issue for disabling most recent items in lookup of D365 CRM.

This chrome extension allows to easily find the logical names of entities. It also allows Dynamics CRM users to perform advanced actions, that normally require bookmarklets. Steps: Install Chrome Extension Link-https://chrome.google.com/webstore/detail/level-up-for-dynamics-crm/bjnkkhimoaclnddigpphpgkfgeggokam   The other major functionalities provided are: Hope this helps!

Offline functionality in Modern POS (MPOS) is critical to business continuity and continuous store operations. MPOS must be available whenever needed, and as a result, it is critical that offline mode is provided for the broadest set of scenarios. Generally Offline functionality is not enabled by default. When you create a store, you need to configure it to run MPOS,  You need to enable Support offline functionality from the register level and on store-level ensure that offline profile is selected. After running the appropriate jobs, offline functionality should work with MPOS in case the internet connection goes out. The offline mode should kick in automatically when the connection with retail HQ or internet goes out. Microsoft has extended this functionality by making an improvement to it. Now you have the ability to switch to offline manually prior to signing in to MPOS.  To do this you need to go to an offline profile and enable allow a manual switch to offline Run Register, Channel Configuration and Offline database configuration jobs. Now open the MPOS App and click on the Hamburger icon at the top left of the screen and go to settings Here you get an option to switch to the offline mode if you want to work offline. The advantage of having this manual mode is that if you don’t have to wait for MPOS to decide whether to switch to the offline mode or not. Hence your time is saved. You can make that decision and proceed with offline or online mode. Hope this helps!

Introduction: Establishing a connection is an important step before developing a solution for Integration. While integrating with Microsoft Dynamics NAV as a source/destination a Connection is needed which can be established as follows. Step 1: Click on “More” tab and choose Connections. Step 2: Click on “Addition” Symbol to add a Connection. Step 3: Install On-Prem Agent on Nav server. Refer to the link below. https://help.scribesoft.com/scribe/en/index.htm#sol/agent/agentinstall.htm?Highlight=On%20prem%20agent Step 4: Add the details as follows. Connector Type: Microsoft Dynamics 365 Business Central/NAV. Name: Give a name for your connection. OData Service URL: Get the required Odata URL from NAV. Note: The URL should end with “Odata” at end. No additional forward slash must be added at the end of the URL which might result in errors. http://ftl-nav-dev:7048/FTL-DEVInstance/OData User: Find it after the date as follows. Password: Password for NAV Company Name: Find it before the date as follows. Agent: Select the On-Prem Agent which you had installed.

Introduction: Converting Date/Time values according to a time zone is quite challenging task in SSRS Reporting. For D365 CRM online we can achieve this using CDate Function. I will demonstrate how to use CDate function with a dynamic time-zone parameter. Step 1: Add this reference to the report properties: Click on “References” and then click on “Add” button under “Add or remove assemblies”. Browse the following file from your BIDS folder. Microsoft.Crm.Reporting.RdlHelper, Version=9.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35 Click on Ok button to save the changes. Step 2: Create the parameter in the report data section in the “Parameters” folder as shown below: In the “Default Values” section check the click on “Add” Button. Enter the User Time Zone in the Formula and click on OK to Save the Changes. Step 3: To use this functionality is simply as follows: DateValue(CDate(Microsoft.Crm.Reporting.RdlHelper.DateTimeUtility.ConvertUtcToLocalTime(Fields!msdyn_dateValue.Value, Parameters!CRM_UserTimeZoneName.Value))) Example: If the Expression or Formula is as follow: Last 30 =WeekdayName(Weekday(DateSerial(Year(Fields!msdyn_dateValue.Value), Month(Fields!msdyn_dateValue.Value),”1″).AddMonths(1).AddDays(-30))) The Replace it with: Last 30= WeekdayName(Weekday(DateSerial(Year(DateValue(CDate(Microsoft.Crm.Reporting.RdlHelper.DateTimeUtility.ConvertUtcToLocalTime(Fields!msdyn_dateValue.Value, Parameters!CRM_UserTimeZoneName.Value)))), Month(DateValue(CDate(Microsoft.Crm.Reporting.RdlHelper.DateTimeUtility.ConvertUtcToLocalTime(Fields!msdyn_dateValue.Value, Parameters!CRM_UserTimeZoneName.Value)))),”1″).AddMonths(1).AddDays(-30))) Note: This is an easy way of dynamically converting a time zone from UTC to the user’s local time using CRM Online. We have to replace all the formulae which contain the DateTime field value which is retrieved directly from FetchXML with the above mentioned Function to avoid issues in SSRS reports due to Time Zone Conversion.

In Dynamics plugin implementations, you might have lengthy complex plugins that makes calls to Dynamics several times. I agree that calls to Dynamics should be as less as possible and use Link Entity as much as possible and the plugin should be well designed to handle such lengthy executions. However, there are instances where these plugins are probably updating some fields that in-turn trigger some other sync processes and the execution begins to take longer than it should. At times, such lengthy executions result in the plugin timing out. In the case of Dynamics 365 Online, the timeout is 2 minutes and you can’t change it. (In on-premise, you can) And now, you need to know what’s taking so long! So I want to propose a method which proved effective for me to identify this. First, in case you are looking to work with Tracing for plugins, here’s a great blog on the same – Debugging Your Plug-ins with the Plug-in Trace Log Add DateTime to Trace Logs One of the best approaches to identify what portion of the plugin execution is actually taking time to process is to keep adding Trace logs and that too, with a timestamp! This will give you an idea of what part of your plugin is taking long to execute and will give you a fair idea if anything needs to be redesigned. Set these traces at the very beginning of your plugin and at all necessary places as well as the very end to cover execution cycle well. And your logs will actually record the time when that operation was hit. So now, you have an idea of how the 2 mins are spent and maybe start troubleshooting in that direction. I hope this quick tip helps!

As we know, Dynamics 365 Commerce is released in the preview version, So in this blog, we will have a quick explanation upon some important “Authoring Tools” that we may need to Customize our Website.   Once we reach our Dynamics 365 Commerce page, We need to click on the Site that we are going to alter. This will take you to the above page. We can see the “Authoring Tools”  highlighted in red box. The highlighted wordy assets in the red box are the valuables that we will be using to change the webpage. Information regarding the highlighted authoring resources: Pages: These are all the pages that your website will have. It contains everything from login to logout. Every page is justified here with status, last user and last modified. 2. Products: This page has all the products that our D365 Retail online store has inside it. Any change in Retail Online Store products will be reflected here. 3. URL’s: These are URL’s of every Specific Page that you can link with another page. You can discard any page(considering you know its URL) through this authoring tool. Also, if you want to link your website to another page then you can do it from here. 4. Templates: Template is the page design used as a starting point for creating pages of your site. When you add a new page to your website, you need to assign a template for it. When you modify this template, the changes cascade to that respective pages on your site.  5. Fragments: In easy words, we can say this can be the upper & lower part of the website that we are designing. Every fragment that you design can have a fragment.  These are small details that you can keep for your website and can make them reflect on each URL you want to.   6. Assets: It allows you to add all your assets(photos/videos) in a single place. You can reuse them every time on whichever webpage you want. Please note: Every authoring tool has its own specific condition that can be customized as per your needs. Also, this is a preview version. Hence, many more changes are expected in future versions. Hope this helps Dynamics e-Commerce builders 🙂

Introduction: Handling Errors is a best practice in Integration when integrating to keep a track of the Errors that occurred during Integration. The Customized Error Handling is Handy to find quick Errors to understand them and resolve as required. This approach can be extended to any Source or Destination as required. Our Scenario: Integration from SalesForce – NAV. Different Approaches to Error Handling: No. Approach Description Customizations Required Comments 1. Entity Level All errors will be logged in an ‘Error Log’ entity in Salesforce and NAV along with the error description and date & time the error occurred. 1. Custom entity ‘Error Log’ 2. Fields for ‘Error Log’ entity: i. Name [String(100)] ii. From Entity [String(100)] iii. Error Message [Note] iv. Record ID [String(100)] v. Created On Date [DateTime]   For instance, i. Name: Error while creating ‘Customer’ in NAV ii. From Entity: Customer iii. Error Message: The specified Country is not valid iv. Record ID: Cust123 v. Created On Date: 08/07/2018   Example:    2. Field Level If an error occurs for a record during integration, the error description will be stored in a custom field on the record in Salesforce or NAV. A custom field ‘Error Description’ will have to be created on the form of all required entities. Field: Error Description: [Note]   For instance, when you open a Customer ‘Cust123’, Error Description: The specified Country is not valid   Example:

Many of the time while building project/solution we came across the “reference is required to compile this module error”. The reason behind this error is that your module’s reference package is missing the required package. In error itself, the missing module can be rectified as shown for example in following screenshot reference to “SourceDocumentationTypes” is not made. Now you have to add a missing reference to your module as follows: Select Update model Parameters from Dynamics 365 >>Model Management>>Update model Parameter Now select the required model name from the model list and click on Next. Now make sure to select the checkbox in front of a required reference from reference packages (In our case SourceDocumentationTypes reference was not there ) and click on next. Now click on finish. Now after attaching a reference to the package build package/Solution and you have solved your error.