x Want to participate? Join the group to interact
Options
  • State Not Answered
  • Replies 1 reply
  • Subscribers 88 subscribers
  • Views 415 views
  • Users 0 members are here
Browse Forums
Announcements
293
topics
370
replies
Business Object Interface
1k
topics
7k
replies
Core Financial Modules
2k
topics
8k
replies
Customization and Productivity
3k
topics
12k
replies
Distribution, Manufacturing, and Applications
2k
topics
7k
replies
General Discussion
1k
topics
3k
replies
Partner Cloud
44
topics
91
replies
Payroll, Time Tracking, and Job Cost
777
topics
1k
replies
Reporting and Analytics
962
topics
3k
replies
Sage CRM for Sage 100
164
topics
357
replies
Technical and Installation
2k
topics
9k
replies
Year-end Forum
89
topics
237
replies
TaylorM

Is the BOI going to stick around for awhile? Is there a better way to communicate with Sage 100

Posted By

I've been working with the Sage 100 BOI for some time now and have done a lot of C# applications that interact with the BOI for all sorts of Sage 100 integrations.  As we all know the "API" is pretty clunky.  I thought about creating a class Library that has generic functions for Creating SO, AP Invoice, etc so I can use it for future projects and possibly put it out on Nuget but I didn't know what the future of the Sage 100 API methodology looks like.  Does anyone out there know?  

I have clients who ask if Sage 100 has a Rest API and I just laugh.  It would be nice if there was an API like there is for Intacct.  Does anyone know if something is in discussion or in the works to improve the Sage 100 API?  Any bit of information I can get on this will help me determine how much time I want to spend on this internal project of mine that might help the community out.  Thanks!  

  • 0

    I don't see BOI going away anytime soon. It is part of the business framework, and it is used by customizer. It is a core part of the product. You would have to adjust your code based on changes in Sage 100 for each release, Product update, or fix. You are interacting with the objects in Sage 100 and as they make changes to it you will have to adjust your application. Sage may publish what is new or changed with the system but doesn't say what changed related to BOI. 

    API has been talked about multiple times on the forum. Sage has some limited options for an API and then there are some 3rd party options, giving more functionality. 

    Sage options would be:

    • Web Services (very limited and not any new development)
    • SData (not as limited but no changes since created and no longer developed)
    • Office 365 connector (Required to be on Microsoft 365 environment. This is currently being developed and has new functions/resources being created, not a lot of users on it and not much documentation. Not sure of roadmap for future, but looks very promising as to what you can do with it)

    Some 3rd party would be:

    • In-Sync with their API - Using their Sync product, they have added an API to the data
    • SDE - Realtime JSON or XML API to Sage 100
    • CimCloud - Using their Sync to their system which has an API interface to the data

    There are other options available for 3rd party, these are just what I am familiar with.

*Community Hub is the new name for Sage City