This post is going to be a rather lengthy introductory course on the Salesforce REST API. If you’re just looking for the Postman collection, or would like to just follow along, click here. We’ll discuss authentication, basic read operations, SOQL queries, batch & composite queries, and querying with an external key. We’ll also touch on the Salesforce workbench.
Inspired by Tim Ferris’s 5-bullet Friday and Scott Hanselman’s Newsletter of Wonderful Things, I’ve decided this would be a great place for me to share some of the humorous, educational, insightful, or just generally weird things I found online. It could be videos, book recommendations, gadgets, recipes, and so on.
We’re going to review how to work around the frequent and ever present error: String or binary data would be truncated. The statement has been terminated.
Many people have heard of Salesforce. Right now, you’re probably thinking of a web portal used by sales people to find new customers, maintain accounts, and track opportunities, and you’d be right to think that. Salesforce is a great platform for CRM, but it’s so much more than that.
Do you ever develop prototypes, or starter projects/accelerators, that you’d like to use again in the future? A good way to do that is by creating custom templates for dotnet. Once completed, anytime you want to create a new project of that type in the future, you can use key in “dotnet new ” and you’re off, complete with correct namespaces. You can even do conditional checks, or variable replacements.
REST services are everywhere. It’s tough to find an application that doesn’t leverage an externally hosted REST service in some way. Prior to .NET Core 2.1, a common library that was used to perform REST requests was RestSharp. I love RestSharp, but let’s explore the new alternative IHttpClientFactory that became available as part of .NET Core 2.1.
This post will walk you through the steps necessary to add a strongly typed appsettings.json configuration file to your console application. I’ll dispense with the formalities of writing a detailed introduction on why you would be interested in doing this and jump right into the steps involved.
NDC Minnesota is the inaugural NDC Conference event for the United States. I’ve long followed the event online as they post most of their conference sessions on Vimeo. The event was held in the very well appointed St. Paul RiverCentre in downtown St. Paul, MN. Absolutely no complaints about the venue, the event itself, or any of the speaker presentations. I honestly was expecting a number of hang-ups since the first year for a conference is usually a learning experience but it feels as though the NDC team is really on top of everything given their past events at other locations.
Front-end frameworks like React, Angular, and Vue are making big waves in software development. Microsoft makes great tooling for working with JS frameworks like those in the form of Visual Studio Code. There is also a large trove of information and tutorials getting setup inside the VS Code environment. One specific resource I really appreciated was Cory House’s Pluralsight course on setting up a JS development environment.
Here is a common scenario for you. You’re building an application… any application. It could be your side project, a sales tool, an ecommerce site, a REST api, a video game, a reporting dashboard. Anything. You’re building your app, and you reach a point that you’d like to try it out, to see how it would look to a user. How do you simulate a production scenario with no data to test with? If you’re lucky, you have data from an existing customer you can use, or there is a sample dataset available online. If you’re unlucky, you’re left generating dummy data using garbage inputs (random strings, random numbers, etc) – data that passes the regex, but doesn’t provide a good simulation.