Recently, some developers asked me about the methods when creating BC development documents. They need to record the Object Type, ID, Name used in the project to the development documents, and they also need a list of AL file names. Is there an easier way?
This is one of the common question that I keep on skipping for a while to write an article about how to export data in Business Central.
The Process is similar but during the Upgrade or writing code we kind of used a function C/AL World CreateBookAndOpenExcel which is not supported with Business Central.
I’m continuously emphasizing that for monitoring cloud applications (like Dynamics 365 Business Central) and cloud services, using Azure Application Insights is a must.
For analyzing telemetry data, I‘ve talked in the past about how to use Log Analytics and the features available in the Azure Portal, how to use Powershell, how to use Power BI and more. But what to do if you want to extract the Application Insights telemetry data and use these data in an external application for different kind of tasks?
Today’s post covers some programming that is not of my own making. My colleague Andreas Rascher has built a damn cool functionality that allows you to export the dataset of RDLC reports in different formats. Since we think the functionality is extremely useful, we didn’t want to keep it from you.
As a Power BI developer I know how Power Query makes it easy to get data from web sources, but I also know there are limits to what it can do. I can get data from tables on web pages, I can get data from web services, but when confronted with a website where you have to click a button to download a file there’s a problem.
Dynamics 365 Business Central allows you to export data from Business Central to Excel for further processing. In some companies, this function is difficult to perform due to certain data processing and monitoring regulations. Administrators can now manage the control of data export to Excel.