In our Org we have quite a few places were data is auto populated based on other data selected. This however comes with allot of rules. When I started, we had allot of issues where sometimes the incorrect data is selected. This required a rewrite of the filtering to find the correct data but often caused the “fix” to break another set of data combinations.
A question I got recently was, how can I visualize or create a dataset that can show/fetch information on a timeline? For example, I have a time-sheet and want to visualize the hours employees worked at certain projects, per day, week, month, year, and so on.
In this example I will create an order intake report. For the simple reason that for this report you can use the standard demo data in Business Central, and for time-sheets you first need to go threw a setup and then create the demo data.
When developing extensions for Dynamics 365 Business Central, you could have scenarios where you want to execute a procedure or a business process only if the extension is running on a SaaS environment or in an on-premise environment (or maybe having a different behaviour accordingly to the environment).
With data clearly taking the position as king in today’s business world, it’s important to have a tool that can help you tame it and use it to your advantage. Microsoft is all about helping you create a “data culture” in your organization—in other words, taking advantage of data across the organization to tackle any problem and meet any goal. Microsoft Power BI does just that…but what about other tools? Yes, there are other options, but there are so many benefits offered by Power BI that we believe it’s clearly the best choice. Here are 5 reasons why we love Power BI:
The Model-View-Controller (MVC) architectural pattern divides the apps into three main components: Model, View and Controller. The MVC pattern lets you create simpler apps to update and test against traditional monolithic apps.
If you’ve ever built a BI solution it’s likely you will have had to integrate third party data, and if that’s the case you will know how painful it often is to get your hands on that data. Badly designed portals you have to log into every week to download the data, CSV files emailed to you, APIs with complex authentication – it’s usually an unreliable, slow and manual process.
If you are like us at Axians Infoma and can’t make the transition of your on-premises solution from C/AL to AL with a single snap of your fingers, you may want to use hybrid deployments as a first step. This means shipping your standard C/AL solution and publishing dependent extensions on top of that to enable a step-by-step migration to AL.