Yesterday I’ve provided a solution for saving a file generated directly from a Dynamics 365 Business Central SaaS tenant to an SFTP server by using Azure Functions. I’ve to admit that this is my preferred way because it gives me more freedom, scalability and adaptability. But obviously, that’s not the only possible way to do so.
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:
At the Microsoft Directions Asia Conference, a team from ArcherPoint attended many sessions and shared their experiences. On a large scale, the conference unveiled the April ’19 Release of Dynamics 365 Business Central as well as announcing the end of Windows Client beginning with the October ’19 release. They also shared best practices for continuing on with Visual Studio Code and AL.
I recently attended the Microsoft Directions Asia Conference for the first time. Eight employees from ArcherPoint participated in or attended nearly 80 sessions presented by Microsoft and ISVs. Team members went to different sessions and shared that knowledge. The experience was awesome.
The other day we found out that some part of one of our extensions was not uploaded to our source code repository and no local version was available anymore. But we did have the .app file. I knew from extensions version 1.0 that the extension file, the .navx, was a zipped set of files. The x in .navx is pointing at this as with all office file extensions now a days.