Using SData 2.0 in Sage CRM: Part 5 - A word on authentication
The final part of the SData 2.0 series for Sage CRM, comparing the available authentication methods and when each one is the best choice.
Blog · Topic
14 articles tagged Sage CRM.
The final part of the SData 2.0 series for Sage CRM, comparing the available authentication methods and when each one is the best choice.
Part four of the SData 2.0 series for Sage CRM, showing how to delete records with the DELETE verb, using examples such as removing a company.
Part two of the SData 2.0 series for Sage CRM, showing how to update existing records with the PATCH verb and a JSON request body, using examples.
Part three of the SData 2.0 series for Sage CRM, showing how to insert new records with the POST verb, using examples such as creating a company.
The first in a series on SData 2.0 in Sage CRM, introducing the RESTful API, how it differs from SData 1.1, and how to query records with Postman.
Renewing or upgrading a client's Sage CRM license means relicensing the system. The short process is laid out step by step, along with its prerequisites.
Synchronizing contacts, appointments, and tasks between Sage CRM and Exchange/Office 365 starts with configuring the integration in Sage CRM, as shown here.
Before Sage CRM can sync with Exchange, Office 365 needs a dedicated user and an impersonation role. The setup is covered step by step.
Logging into Sage CRM over HTTPS with Internet Explorer can trigger a "Browser session mismatch" error. The cause and the fix are explained.
A domain change can leave the Sage CRM application pool without file permissions, causing a "Cannot create file" error in reports. Granting access fixes it.
A mysterious humbs.db attachment can get Sage CRM emails flagged as spam. Disabling thumbnail caching and removing existing attachments resolves it.
A July 2018 Windows update can break Sage CRM .NET pages with a "Class not registered" error. A small IIS authentication change resolves it.
Sage CRM document uploads can fail with an "UnexpectedEvent" error when document type codes are too long. The cause and the fix are explained here.
A Visual Studio extension speeds up .NET development for Sage CRM, bundling project templates, item templates, and snippets for commonly used components.