Skip to Content

What is the difference between 'SAP B1 Studio', 'Screen Painter' and 'B1DE'?

Hi,

I am still a newbie in SDK although I have developed a few successful applications (add-ons) in SDK with generous help from the forum.

But I have been developing entirely in code (mainly because the Samples in SDK are in code). Although long and painful, coding has helped me understand SDK.

Now, I wish to develop add-ons using a graphical tool.

If I am not mistaken, all 3 methods can be used for developing add-ons.

Could anyone explain to me which method is best for developing and registering add-ons in SAP B1?

What are the advantages and limitations of each method?

I now understand the difference between SDK and B1DE after reading this:

I use SAP B1 ver.9 and VB.NET 2010

Thanks

Leon Lai

Add a comment
10|10000 characters needed characters exceeded

Related questions

1 Answer

  • Best Answer
    Posted on Dec 16, 2014 at 02:46 PM

    Hi Leon,

    The Screen Painter is merely a tool to design forms. It will allow you to create a form using a visual editor and then save to an xml (or srf) file. You can't really develop an entire addon just with Screen Painter. But it is a great tool to assist in quickly creating your forms.

    The B1DE is a set of tools that allows you to create your addon from scratch. The good thing about B1DE is that it's easy to use and integrated with Visual Studio. However this tool is no longer under active development by the original authors. Still, you can develop your addon and create your installer using the several wizards available. Another advantage is you can modify the source code because it's available to everyone.

    B1 Studio is the "next generation" development environment. It's fairly recent compared to the other too, but it integrates well into visual studio and there is also a standalone version that you can launch from B1. However, because it's recent it still has some issues (several threads on the forum have shown that). But all of them actually have some issue. A great advantage is that B1 Studio is trying to close the gap between the way you develop Windows Forms applications and a B1 Addon. It uses familiar elements like double clicking an event name generates the method that handles that event.

    Could anyone explain to me which method is best for developing and registering add-ons in SAP B1?

    There isn't a best approach. All these things are just tools to help you build your addon (the SDK alone allows you to build a full addon without any of these tools).

    It will always depend on what you intend to do. And all we can offer is advantages and disadvantages based on the situation. For example, if I was building a single screen addon to be used by 1 or 2 users tops, I'd go with B1 Studio. It will be fairly fast and since this is a very small application not many problems will be expected. If I need a bigger addon, but I need to do it very fast but also for a small set of users I'd go with B1DE. However, if I'm building a huge addon to be used by multiple users, and to be used in multiple versions and localizations, I'd go with the basic SDK (merely because everything would be under our own control and not some framework).

    Conclusion:

    Try them all, build some spike solutions to check their advantages and disadvantages and then decide based on real experiences.

    Good luck.


    Best regards,

    Pedro Magueija


    View Pedro Magueija's profile on LinkedIn

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.