Why it is required? Let’s discuss the scenario where we will be required to have some records in the Multiple Environment. Let’s say we have workflow or flow which is configured or running with specific records. So, if we move the flow or workflow to another organization or Instance so the same record is not available with the same GUID. To run the flow or workflow we must change the flow or workflow. Now if we have 10 – 20 flow / Workflow like the same, then it will be so much time consuming So, the best solution to have the Same records with the same GUID in multiple instances. Prerequisite: The system must have the same entity and fields present in both the system in which you must transfer records. Because it will through an error while import to destination Environment Solution: Exporting Phase: Login to Source Environment from where you want to export the Data. Open the Entity of which data needs to be migrated. You can see I have an Entity called Customer which is having a few numbers of records present in the system. Now You need to export the Data from the source Environment. Export Data from the advance find or direct from the View. After Exporting the Data from the system, an excel file will be downloaded with the same columns as in the views. Now, open the exported Data file. The following is the screenshot of the file. You can see there will hidden Columns in Excel A, B, and C. Now to Unhide the Hidden Columns, select all Data Or Press Ctrl + A and Go to Format in Home Section > Under the Visibility Section Click on Hide & Unhide > Unhide Columns. Please see the following Screenshot for more reference. Now You can see all the three Columns as (Do Not Modify) Entity Name, (Do Not Modify) Row Checksum & (Do Not Modify) Modified On. You can see the Hidden Column in the screenshot after unhiding. Let’s move forward now, we must delete (Do Not Modify) Row Checksum & (Do Not Modify) Modified on Columns because we are not required those columns while importing to another environment. If we will import with those columns it will through the error while import Operation. Change the Header from (Do not Modify) Entity_name to Entity_name for convenience while mapping during importing and Save as CSV. Now Your File is ready to import in another system. Let’s go towards the importing phase.

Introduction It is important for the end-user to understand the error displayed on D365 Portals. In this blog, we will display D365 Plugin Error on the D365 Portals. By default, the error will be displayed as shown below: Implementation Step 1: Create a new Site Setting record. Step 2: Set the values given below in the fields: Name: Site/EnableCustomPluginError Value: true Now you can see the Error thrown by D365 Plugin. Custom plugin errors will appear on the following screens: Entity list Retrieval of records Entity form Retrieve Create/Update and so on Web forms Retrieve Create/Update and so on

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

The tips for formating SSRS reports have been covered here. The Default margin settings have been given as to avoid the blank page issue And give the report a formal look. Also, how to Align Page Number in center of the page has been showed. Default margin settings:- Aligning Page Number in center of the page :- Select Page Number Text Box-> Format->Center in Form Hope this helps! For more such blogs refer the below link. https://www.cloudfronts.com/how-to-use-level-up-for-dynamics-365-crm/

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.

Microsoft Excel has traditionally been the go-to reporting tool for businesses, but Power BI offers powerful analytics and reporting features for organizations. With faster experimentation with visualizations, statistical functions and calculations across broad datasets and ability to derive answers on the fly through the rapid recombination of fields, it is clear that Power BI delivers far greater insight than Excel. Reasons Why You Should Migrate Reporting from Excel to Power BI: 1. Storing and Accessing Large amount of Data Power BI has very impressive compression abilities for Microsoft Excel and text/.csv files, which allows you to view, analyze and visualize huge quantities of data that cannot be opened in Excel. Large datasets don’t have to be cut down in size and aggregated to show more encompassing analysis. 2.Applications Excel does have some of the newer charts now, they can’t connect to the data model. But Power BI is ideal for Dashboards, alerts, KPIs, and visualizations, including analyzing your data visually. 3.Reports Excel reports are normal and ordinary comparing Power BI whereas Power BI offers Beautiful branded reports comparing Excel. 4.Cross Filtering Power BI allows advanced features in Cross filtering between charts unlike excel. 5.Dashboard Refreshment You can refresh data in Power BI. Excel does not allow dashboard refreshment. 6.DataSet Power BI has the capability of handling larger dataset. Excel can handle limited dataset only. 7. Incredible Cloud-based Features Once you have finished constructing your Power BI analysis, you need a way to publish and disseminate your dashboards and reports. In Excel this would typically involve emailing a large file around, putting it in a shared drive or SharePoint portal, and letting people know it has been updated.With Power BI offered “publish” this process has been completely revolutionized. 8.Natural Language Query This incredible feature allows users to type questions and get an answer, either in a default or user-specified form. This is useful for executives with specific questions and business users who are unfamiliar with Power BI or the data model behind the report. Power BI is an easy tool to use that helps propel organizations into a data driven culture. With powerful self-service abilities, no longer are business users dependent on IT for gathering, transforming and analyzing data. Automation of dataset integration, ease of expansion into new data sources, rapid visualizations, and easily deployable Row Level Security are amongst the many reasons Power BI is a necessity.Additionally, a cloud-based collaboration environment with features like Natural Language Query ease the process of data governance. In the age of analytics, it’s import for organizations to intelligently utilize the data they collect to rapidly evolve with changing business and consumer habits. For more such blogs refer the below link. https://www.cloudfronts.com/how-to-use-level-up-for-dynamics-365-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: Use the Update Block to update existing records in the source or target datastore. While integrating with Microsoft Dynamics NAV as a destination use the Update Merge Block to perform the Update Operation in Microsoft Dynamics NAV. The Update Merge block can configured as follows. General Tab Following Options are available under the General Tab. Change the Block Label Add Description Set Batch Processing Options Select the entity to use for this Operation. Matching Criteria Tab Following Options are available under the Matching Tab. Specify one or more fields in your source and target data to select records for this operation. Fields Tab Following Options are available under the Fields Tab. Map the required fields from your source to destination directly or based on some formulae. Note: The following fields must Hardcoded Error Handling Tab Following Options are available under the Error Handling Tab. When an operation fails — If the record cannot be updated, an error is logged. If no matches are found — If the record being processed does not match the criteria in the Matching Criteria Tab, it is not updated, and an error is logged. Errors and Warnings Tab Following Options are available under the Errors And Warnings Tab. Various Errors available are displayed. Once you have corrected the errors click on Validate button to update the Errors and Warnings Tab.

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.