Withing simple steps you can solve this problem. You need to upload your Microsoft Dynamics NAV license first, Then you need to restart the service.

For upload license, Go to tools then License Information. Then Choose upload option and upload the license. After that you need to restart your Dynamics NAV service.

Finally you will solve the problem.

The post The license information on the Microsoft Dynamics NAV Database Server is invalid appeared first on Shan Abeywickrama | Dynamics NAV & Business Central Insights.

Microsoft Dynamics NAV
—————————

Break On Error Message:

Table ID must not be 14 in Default Dimension Table ID=’14’,No.=”,Dimension Code=”.
—————————
OK
—————————

Not like this, but you will get the slimier one. Let me explain this scenario.

Some one added two fields in location table which are linked in to dimension value table (Like shortcut dimension 1 and 2). When I debug the error it was trigger from default dimension table .

If you press F9 on Table ID  field you will see code like bellow.

CALCFIELDS(“Table Caption”);
DimMgt.SetupObjectNoList(TempObject);
TempObject.Type := TempObject.Type::Table;
TempObject.ID := “Table ID”;
IF NOT TempObject.FIND THEN
 FIELDERROR(“Table ID”);

So I went into DimMgt.SetupObjectNoList. 

If you clearly look into the function code like this.

Simply I add a line by mentioning the  table . In my case it is Location and it was not there before So I added Location. But keep remember you need to increase the dimension value in TableIDArray variable. So previously it was 25, I have increased and new value is 26.

The post Table ID must not be 14 in Default Dimension Table ID=’14’,No.=”,Dimension Code=” appeared first on Shan Abeywickrama | Dynamics NAV & Business Central Insights.

This is an invalid type of primary key for the autosplitkey facility. It should be Integer/BigInteger/Decimal/GUID.

This is why, If you use the property of Autosplitkey as Yes, It is necessary to end your primary key with integer.As a example,if you use bellow combination and set Yes in Autosplitkey, you will get above error. My example I have primary key like this Document No.,Line No.,Date .This is not ending with Integer Type .So if you create like this (Document No.,Date,Line No.) you never get this error.

Lesson learned :: If you really want to use Autoslitkey property , You should have Integer type filed at the end of the Primary Key . 

NOTE ::: DO NOT CHANGE PRIMARY KEY IN DYNAMICS NAV BASE TABLE.

---

 

The post Error “This is an invalid type of primary key for the autosplitkey facility” appeared first on Shan Abeywickrama | Dynamics NAV & Business Central Insights.