Sunday, March 29, 2020

Learning Business Central Development From Scratch: FLF license files

By Steve Endow

As I mentioned in my prior post in this series, I'm starting from absolute scratch when it comes to learning Dynamics 365 Business Central development.  I'm clearly not an expert at this point, so if you find any information in the post that is inaccurate, please let me know.

I've spent months learning how to install and configure Business Central Docker containers, including the many, many quirks of that process.  I've been trying to create a blog post and video on that for months, but given all of the details I want to cover, it's very tedious to prepare and still not complete.

So in the meantime, I thought I would write about one specific detail that I learned while trying to setup a Business Central Docker container.  This post is one of those asides.

As a result of my "newness" (ignorance), I'm running into small issues that are probably obvious to any experienced NAV and Business Central developers, but cause me to stop what I'm doing and spend 15 minutes, 30 minutes, or perhaps several hours to figure out.

The Business Central FLF license file is one of those issues.  Coming from the Dynamics GP world, I know nothing about NAV or BC licenses or license files or how licensing works in BC, other than the user-based licensing for BC SaaS.

If you are going to be working with Business Central Docker containers and include automated testing (which you should!), I suspect you'll need to know about FLF license files.

NAV Container Helper - Include Test Toolkit

Above is a sample call to the NavContainer Helper PowerShell script.  Notice the parameter on the last line:  includeTestToolkit.

How many digits can a Business Central Amount field actually support?

 by Steve Endow (If anyone has a technical explanation for the discrepancy between the Docs and the BC behavior, let me know!) On Sunday nig...