Skip to Content
avatar image
Former Member

SBO-SDK Consult: Add-ons Collision Clarification

Hi all,

Since there are several calls regarding Add-on collisions,

I would like to take this opportunity to clear up this subject.

SAP Business One, as other Windows applications, is an event driven application and

was designed to run in parallel with partner Add-ons.

The events are being sent to the Add-ons according to the order they were raised.

Different Add-ons may catch the same event and handle it differently (BubbleEvent wise).

This will create a situation where one Add-on sets the BubbleEvent to False

while all other Add-ons wait for the core code to be executed.

This might get even worse when partners will be allowed to add their own DLLs to SAP Business One.

Bottom line:

1. Add-on collisions are under partner's responsibility. Partners should handle these kinds of problems themselves.

2. Partners can discuss their collision problems in the SDN for faster and suitable solution.

Best regards,

Yaniv Gamliel

SDK Consultant

SAP Manage Israel

Add comment
10|10000 characters needed characters exceeded

  • Follow
  • Get RSS Feed

1 Answer

  • avatar image
    Former Member
    May 19, 2004 at 02:16 PM

    Dear all SBO and SDK interesting people

    I’am realy very surprised, to read such a message in this forum.

    If this statement would be correct, it would have on all SBO developer in the whole world devastating consequences. Additional would thereby fall a main argument against our largest competitor. Up from now, all Add-on-developers has to develop on SAP source code (is this possible?)

    As a partner, with not few SBO customers and many SDK developments, we would like to express our opinion:

    1. The responsibility to SDK and the containing functions lies to 100% to SAP.

    2. To reach the most published goal, the SDK must manage many different Add-ons, also on the simultaneous using.

    3. The most knowing collision problems with Add-ons, concern mainly addons together with SAP Add-ons like ‘payment engine’ or ‘dtw’. It can’t be only an affair between partners. In that case SAP must be an equivalent partner too.

    4. The planned SDK concept was, with different development environments (VB, C++ and others) to access and using all the SBO objects. Should this really be able to do without any events? How?

    5. The only way to solve the problem with events on different orders would be, each Add-on developer has to describe and list all used events in his own tool. The developer of the ‘payment engine’ (it means SAP) stays here on the same rule.

    6. Partners is allowed to create own solutions by the SDK. This is a contractually assured warranty of SAP.

    I would really like to call all developers (on both side, partners and SAP) and all members of the management-team, to work together for a future-oriented solution.

    Regards

    Jürg Aerni

    Manager Software Department

    Steffen Informatik AG

    Switzerland

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member

      Dear Mr. Aerni,

      I fully agree with you that Add-Ons provided by SAP have to follow the same rules as the Add-Ons of the partners do. If you are aware of any collisions which might occur by using the SAP Add-Ons you should open an error message.

      Best regards,

      Achim Magel