In this video, I take a look at what’s inside the app files we creating when compiling extensions for Business Central.
Source code files are living things. We add new ones and change their content on daily basis. Occasionally we delete them, too. Git is amazingly efficient when it comes to tracking these kinds of changes.
However, sometimes we need to change the file name, or file path, or both. And if you are an AL developer who has ever transformed a C/AL project into AL, you have probably done this at least once, for all .al files in the project.
Transferring data from Business Central Tables through API is one of the latest version of transferring data from or to Business Central using the API Page Objects or Web Services.
Well, it gets a little difficult to transfer file blobs using the Media.ReadLinks and Media.EditLinks JSON field.
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: