Sage 50 SDK / API requires the Sage 50 desktop UI to remain open.
Sage 50 .NET already has this ability implemented exactly how the Sage 50 COM SDK / API should be implemented.
Below is a screen shot of the Company Summary screen. Complex screens like this one, either for a system entity or a custom entity, can be built using the APIs.
A partial rebuild of the Company Summary Screen using the .NET API is actually included…
A customer uses an external system to generate marketing emails to contacts. These contacts exist as records in their accounting system that is integrated with Sage CRM. This means that the contact exists in both Sage CRM and the Sage BMS but because…
A customer had a question on how they could resize a table to fit correctly in their web page.
Below is an image that shows a simple page created by the Self Service API.
The code below shows how the display of List Pages can be controlled in Self…
A customer had a requirement for a summary screen for a custom entity to provide a new company and new person button similar to the core system entities within Sage CRM.
I have assumed that the custom entity pages have been built using the classic ASP…
A customer had the requirement to allow users to export opportunity information to a file that could be opened in Excel.
I have provided below some example code that is designed to be called from a Button Group associated with the System Action OpportunityList…
The document upload into Sage CRM is designed to allow the easy upload of files on an Ad Hoc basis. The document upload feature (at the time of writing this article) differs slightly depending on which browser you use. But it can be time consuming to…
A customer had a requirement to understand the way in which the Dedupe screens for a Custom Entity worked.
The customer had created a new entity that was the child of Companies and Persons and they had added the look up fields into the Dedupe screen…