Bugs in DI API ?

[olivier_huet3]

Hello all,

With SBO2005 PL14, when we import purchase invoices, we have the following errors for a few number of documents :

[PCH1.WhsCode][line: 5] , 'This entry already exists in the following tables (ODBC -2035)'

and

No matching records found (ODBC -2028)

With SBO2005 PL22, we no longer have the "This entry..." error, but we still have the "no maching records found" error.

Wit SBO2007 PL06, we no longer have the "no matching records found" error.... but we still have then "This entry..." :'(

Does someone else have this problems ?

Or, does someone have any idea to bypass this problems ?

More info :

- More than 90% of the documents are ok, less than 10% fails with this errors

- A lot of products have serial number (only 1 serial number by document line)

- We have already checked that serial number not already exists in the database

- Of course, we have already checked that products, vendor, warehouse, vatgroup, exists in the database

[Eneveux]

Olivier,

Is your add-on a .Net add-on? If so, have you tried using the .Net Profiler tool that is part of the Business One Test Tools (B1TE)? This will assist you in narrowing down the issue. You can find B1TE here ...

https://www.sdn.sap.com/irj/sdn/developerareas/businessone?rid=/webcontent/uuid/cbb70163-0c01-0010-9... [original link is broken]

Eddy

[olivier_huet3]

Thanks for the answers.

I've not tried with other serials number for this document, but the serials with the same format are ok on other documents (NNNLLNNN where N are numbers and L are letters, for example)

.Net Profiler give me no issue, and the output is not very helpfull...

btw, yesterday I tried something that seems to work for the "no matching records" error.

Let's take this invoice for exemple :

Vendor : DUPONT

Line1 : Ref. Product= PROD1, Qty=1, Price=10, Serial=123AB456

Line2 : Ref. Product= PROD2, Qty=1, Price=20, Serial=124AB456

Line3 : Ref. Product= PROD2, Qty=1, Price=20, Serial=124AB457

Line4 : Ref. Product= PROD3, Qty=1, Price=10, Serial=125AB456

Previously, I wrote the invoice in SBO exactly like the invoice above.

Now, I write this one :

Vendor : DUPONT

Line1 : Ref. Product= PROD1, Qty=1, Price=10, Serial=123AB456

Line2 : Ref. Product= PROD2, Qty=2, Price=40, Serials=124AB456, 124AB457

Line3 : Ref. Product= PROD3, Qty=1, Price=10, Serial=125AB456

You can see I group the lines by the item code.

I don't know exactly why, but when I do this, I have not the error "no matching records"...

Remember: "no matching errors" is shown with 2005PL14 and 2005PL22 but not with 2007PL06... I tried the group by item on PL22 and I have no error

I will now try with PL14 to see if I still get the "Already exists" error...

[Former Member]

Hi,

Is this error with standard product or with any add-on running.

I faced this kind of problem with I did some code in After Action (Before Action False). And I managed to write that logic in some other place.

If any add-ons are running try after stopping those add-ons.

From a forum thread I also understood that SP_TRANSACTION_NOTIFICATION stored procedure caused some problem with SBO DB Transaction. If you changed anything there, try with stand SP that comes from SBO Help Database.

Try same with any Standard Help DB to reproduce this issue.

HTH

B Ravi Shankar

[olivier_huet3]

Thanks for your answer.

I use only DI API, SBO is not running (and there is no add-on on this database)

I've not changed anything in sp_transaction_notification.

I cannot try with any standard help DB because I have this errors for only a few number of documents....

If I want use a standard help DB I have to import all of the products, vendors, vat account, ... and so it will be exactly like my DB

[Former Member]

Have you tried feeding same information such as vendor, Tax Details, Item details but with different serial in standard product?

B Ravi Shankar