The Power BI team recently shipped some cool new flow options and one of them is really cool. Many times I hear of reports and dataset that fully rely on SharePoint lists. These lists are used by business groups that don’t have the rights to spin up and Azure SQL database or just want to keep a simple list to store their dimensions. SharePoint lists are great for that.
During NAV TechDays 2019 there were a lot of sessions that I would describe as “develop Business Central doing minimum development using AL“. Sounds weird? For me yes… at least at the beginning.
Speakers, such as Arend-Jan Kauffmann (https://www.youtube.com/watch?v=cp848e9WBFs), showed how to connect Business Central with Power Apps or use Power Automate (previously named Flow) and our BC. And my first impression was – noooo way it can be so easy.
I think that many of you on your Dynamics NAV or Dynamics 365 Business Central projects have tasks executed by using console applications (.exe) scheduled by using Windows Task Scheduler or other systems. This works good for on-premise environments (just take your .exe application, create a new schedule with Windows Task Scheduler and you’re ready to go), but what about using these .exe applications on a SaaS environment?
So now – “let’s get started” with ..
Why would I rename all my AL-files?
Well – because of Microsoft and their new (upcoming) code analysis rule about file name conventions. You might already have complied with their previous conventions, and … they will change. Even better: they actually already changed .. Just read here: