x Want to participate? Join the group to interact
  • State Verified Answer
  • Replies 5 replies
  • Subscribers 21 subscribers
  • Views 271 views
  • Users 0 members are here
Browse Forums
Announcements
664
topics
57
replies
General Discussion
2k
topics
5k
replies
Intelligence Reporting
350
topics
840
replies
francoist

SDK Inventory Transaction Item blocked

SOLVED
Posted By

EVO SDK version: 7.10.0 (7.10.0.39)

I am receiving the following error when trying to integrate with EVO. Inventory account '113/2/2/1' is blocked and cannot be posted to.

The application is a well-established application of over 10 years, so we know that the application works well.

We tested by using an Item that does not contain "/" and it works fine.

Our conclusion is that the SDK throws an error because of the "/" character in the item code.

  • 0

    Good Morning Francois

    Please send your query to the Sage 200 Evolution SDK and API Support Team at:

    [email protected]

    Kind Regards

    Bennie 

  • +1
    verified answer 
    The issue is and it does qualify as a bug.
    EVO allows for duplicate Code in their table     StkItem. 
    We picked up that the database had 2 records with the same Code and the first Code was InActive.
    This select will help you find the duplicates.
    Will report to EVO it should use the active code when you interact with the SDK.

    `SELECT Code FROM StkItem GROUP BY Code HAVING COUNT(Code) > 1
  • 0 in reply to francoist

    Hi Francois

    If you have an item with item code AAA, and you then try to create a new item code in th front end, also with item code AAA, Evolution will not allow you. 

    Correct? Slight smile

  • 0 in reply to Bennie Pienaar

    I would hope so, this client on version 7. The EVO consultants sometimes do data maintenance and alterations. It can be prevented if EVO adds a DB constraint on the DB. Alternatively add a check in the application (SDK), if the DB cannot constrain you want your application to be resilient enough to handle.

  • 0 in reply to francoist

    Yip, I agree Francois.

    The front end will prevent it, but doing it via the backend does not yet have a built in constraint to prevent it.

    Any ways, please feel free to log it as a product suggestion using the link below. 

    https://app.smartsheet.com/b/form/4c5023eeaff24b05839f55753b05c465

    If we implement it, it will also improve any SDK and API integrations!

    Blessings!

    Bennie

*Community Hub is the new name for Sage City