Install license for new objects (tables) not detected in customer environment

Hello, first you should make sure that to import the .flf file into the SQL Server database rather than just loading it for your active session. If you uploaded the license using the Web Client or the Dynamics NAV Administration Shell, the new object range will not be recognized until you restart the Microsoft Dynamics NAV Server instance using the Restart-NAVServerInstance PowerShell cmdlet.

If the issue persists after the service restart, you should verify that the license actually contains the newly purchased table objects by opening the License Permission table within the development environment to check your allowed object ID boundaries.

The additional tables become available only if the correct license file is imported into the correct database/server instance and the platform version supports that license format.

To verify the steps and what might be missing:

1. Confirm the correct license file and format
   • For Business Central/NAV, non-demo licenses must be named fin.flf (legacy) or fin.bclicense (new format). Demo licenses use CRONUS.flf or CRONUS.bclicense and should not be used in production.
   • If both .flf and .bclicense were delivered, and the environment supports .bclicense (versions 17.12, 18.7, 19.1 and later), prefer importing the .bclicense file because large .flf files can cause import issues.
2. Make sure the license is uploaded to the correct database
   • For on‑premises Business Central/NAV, uploading the license is done per database, not per client. If there are multiple databases or environments (test, production), ensure the license is imported into the database where the customer objects (tables) exist.
   • If upgrading or running Business Central v17 or later, import the license to the server instance using PowerShell:

          Import-NAVServerLicense -ServerInstance <server instance name> -LicenseFile <path and file name>
          Restart-NAVServerInstance -ServerInstance <server instance name>
     

   • After import, restart the server instance so the new license is applied.
3. Verify permissions and roles when saving the license
   • The account used to upload the license must have the required SQL Server roles/permissions on the database. If the upload fails silently due to insufficient permissions, the old license remains in effect and the new tables will not be licensed.
4. Confirm that the license actually contains the new tables
   • Ensure that the .flf/.bclicense received is the updated license that includes the 10 additional tables, not an older or demo license.
   • If the license was downloaded from a portal (CustomerSource/VOICE for NAV/Business Central), verify that the latest license file was downloaded after the new objects were added to the license.
5. Check that the application objects (tables) exist in the database
   • Licensing only grants permission to use objects; it does not create them. The new tables must be present in the database (imported/merged via application objects or CUs). If the tables are not in the object list, they will not appear even if licensed.

If, after confirming the above, the tables still do not appear as licensed, re‑download the latest license from the appropriate portal and re‑import it into the correct database/server instance, then restart the service.

References:

• Uploading the license file for Business Central on-premises
• Upgrading unmodified C/AL application to version 17
• How to install a Microsoft Dynamics NAV 2017 cumulative update
• How to install a Microsoft Dynamics NAV 2018 cumulative update