When importing my .flf license file, the contracted object range is not reflected.

Question

When importing my .flf license file, the contracted object range is not reflected.

Luis Enrique Robles Coronel 0

I placed an order for my customer for 10 additional tables (Dynamics NAV 2018). We followed the same process we have always used, received the .flf file, and after loading it into the customer’s Dynamics NAV environment, it appears that the 10 additional tables were added to the licensed modules. However, I am unable to determine the range of object IDs enabled for these tables.

On the other hand, we reviewed the TXT license files “Permission Report Detailed” and “Permission Report Summary” obtained from PartnerSource as part of the licensing information, and we were able to see the existing object ranges for tables. However, we still cannot identify the object ID range for which we now have permission related to the newly acquired 10 tables.

My understanding is that we are following the same procedure as always. What could be causing this issue?

0 comments

1 answer

Your answer

Answer 1

The contracted object range for additional tables is not determined or exposed by the .flf license file itself; instead, object ID ranges are defined and controlled by the overall NAV/Business Central object range model and the specific ranges assigned to partners or solutions.

In Dynamics NAV/Business Central, object IDs are organized into predefined ranges (for example, partner and RSP ranges). For Business Central, ranges such as 1,000,000–69,999,999 are reserved for the Registered Solution Program (RSP), and 70,000,000–74,999,999 are for partner-assigned extensions. These ranges are not dynamically changed or newly created by adding “N more tables” to a license; the license update increases the count of objects allowed within the applicable range(s), but the range boundaries themselves remain those defined by the platform and the partner’s allocation.

Because of this, importing the updated .flf will show that the number of licensed tables has increased, but the permission reports will still list the same object ID ranges as before. The additional 10 tables are consumed within the existing licensed range, not in a newly listed range, so no new range appears in the Permission Report Detailed/Summary.

In other words, the behavior being observed—more licensed tables but no new or changed object ID range in the permission reports—is expected and is caused by the fact that the license update only increases the quota of tables within the already-assigned range, rather than granting a new explicit object ID range that would show up separately in the reports.

References:

Object ranges in Business Central