[NNM1] , 'No matching records found (ODBC -2028)'

Hello Ajith

Business One document numbering mechanism in release 2004 changed as follows: The table NNM1 defines the document series characteristic (without relation to the object). The table NNM3 defines the Object to Series relation.

The primary key in NNM1 until version 2004 was the object name and the series ID. In order to support the new concept of the series, the primary key is only the series due to this fact the values of the series was changed so it can be unique.

Set oDoc = oCompany.GetBusinessObject(oInvoices)

oDoc.Series = 2

Until Business One release 2004, the code lines above referred to series no. 2 of the Invoice business object (in NNM1):

ObjectCode = 13 (object code of Invoice)

Series=2

From release Business One 2004 code lines above will refer to an absolute code – series no. 2

NNM1 table was changed in the upgrade process in order to have unique values for the series, for example:

ObjectCode Series ==> Series

-

....---- -......... -----

13..............0...............1000

13..............1...............1001

13..............2...............1002

17..............0...............1003

…...............…...............…

This is the reason your add-on has compatibility problems

If the code includes hard coded assignment to the Series property of the Document object, it should be changed to the new unique key of the series

SAP recommendation is to avoid use of any field value hard coded in add-on code.

Regards, Avi.