Speed up batch data sync from Business Central to Dataverse

Imagine a situation when we have a big table in the Business Central which we need to sync to the Dataverse. By “big table” I mean a table with more than 75000 records.

Why 75K of records? By default, each sync job has a timeout of 12 hours. Of course, you can increase it, but this is not a way. By my measurement, 75K of records is a number that you can sync from Business Central to Dataverse for 12 hours. This time is changing from sync to sync, it could be even 10 hours, but if no issues occurs – 12 hours seems like a maximum time when 75K of any table will be sync to the Dataverse. I checked this with a ~ 25 tables and a result is quite the same everywhere and not very different even with increasing of field numbers.

Source : Andrey Baludin
Read more…

Business Central 2021 wave 2 (BC19): In-depth testing for Force Sync mode in Production Environment (Renaming tables, Renaming fields, Changing field type…)

Last month I shared a new feature in Business Central 2021 wave 2 (BC19), Force sync of customer-specific extensions in online environments (ForceSync mode in Production Environment) I saw some questions after that, for example, if we keep the table no. and field No., will data be lost in Production Environment?

So in this post, I would like to briefly test some common scenarios, hope this will help.

Source : Dynamics 365 Lab
Read more…

Sync Slicers & Sync Slicers Advanced Options

Power BI Bookmarks, Synced Slicers and Selections; these features transformed the way we report using Power BI. Now, most of the business users want reports with actionable interactivity. Well, it has pros and cons; today’s post is not to discuss that but to talk about Synced Slicers.

Synced Slicers were one of the most requested features. As the name says, this functionality enables you to Sync slicers among various Power BI Report pages, and you can manage the properties of it under Sync Slicers Pane.

Bron : Prathy’s Blog
Lees meer…

Using SQL Data Sync with Microsoft Dynamics NAV on-premise and Azure SQL Database

In many Microsoft Dynamics NAV implementations we have situations where the NAV database is often “coupled” with a second database for business intelligence processing or other data manipulations/analysis. Often we use this scenario for handling Power BI data warehouses in the cloud (Azure SQL) that work by using data that comes from NAV, external sources, IoT devices and so on.

Bron : Stefano Demiliani
Lees meer…