SOQL IN Operator in Salesforce
When writing SOQL queries we can use the IN operator or the = operator as long as we are using variables instead of hardcoded strings. This works because the result will be identical.
Insights, guides, and deep dives from the Enterprise Software Academy team.
When writing SOQL queries we can use the IN operator or the = operator as long as we are using variables instead of hardcoded strings. This works because the result will be identical.
This past year, Salesforce has finally released some security enhancements that can make our lives easier as developers. There's two enhancements that can really improve our code and reduce the use of the Schema.sObjectType methods.
Adding a valid DKIM record to NetSuite is pretty easy! Follow these instructions to get it done in a few minutes.
Programming on any cloud platform can be a really frustrating experience. NetSuite has a lot of the same quirks and annoying things that other platforms have whether it be Salesforce, SharePoint, or something else.
Auditing the number of users and who the power users are of NetSuite is unfortunately one of those things Administrators need to…
As you may recall, in Salesforce, there are some fairly stringent governor limits that can cause things to unexpectedly fail. In this blog post, you will learn three easy steps to bulkify any method in Apex.
An outbound message sends information in XML format using SOAP to a specific URL endpoint. The information contains the fields specified when the outbound message is created.
It's not possible to modify Apex code directly in production so doing deletes can be really difficult. In production, Apex classes and triggers cannot be deleted declaratively so we need to go through a special deployment process.
Understanding what Salesforce Integration Pattern to use is vital to a successful Salesforce implementation. Choosing the wrong pattern can result in a really weak architecture that fails regularly, or costs a lot.
The first step for a successful integration is understanding the goals, planning and documenting the current processes. The most important thing is to understand the stakeholders and what they need to do with the data.
Moving data between systems consistently through an integration can be difficult especially given all of the limits that Salesforce throws at us! The purpose of this blog post is talk about all of the common reasons that a Salesforce integration could fail.
When we integrate something we are connecting two applications or systems together so they can talk to each other and share data. There's a lot of business benefits to integrating Salesforce with other systems whether it be your enterprise resource planning system (ERP), your accounting software (Quickbooks, Simply Accounting, etc), or even your case management system.
Salesforce has really transformed a lot of companies I've been involved with because it's made the sales team way more effective and allowed all people that need access to know what's going on. Integrating Salesforce with other apps has the potential to dramatically improve efficiency and productivity in businesses.
SOAP is basically an XML based API that existed before the REST API existed. SOAP stands for Simple Object Access Protocol - it's a mostly legacy protocol that was designed for doing remote api requests in a language independent way. From time to time unfortunately, we'll need to call a SOAP API.
Release notes are usually written in the present tense and provide details about any changes in a new software version.
The big reason to implement an enterprise resource planning platform like NetSuite is to be able to make data driven decisions. In this post, we look at the different "reporting" tools available in NetSuite.
Having your application / system produce the right amount and quality of logs is just as important as having the system process the needed data because it helps make debugging easier and allows us to better optimize data. Logging on AWS lambda can be really costly if it's not done correctly.
Cloud computing is basically using servers whether they be for databases, storage, application or something else through the internet. Cloud computing's inherent strengths are elasticity, ability to automate infrastructure management, enhanced reliability and reduced cost.
For the most part, it seems to be that NodeSQL databases are the defacto standard with Node and JavaScript developers. Using MySQL is still an option and can make a lot of sense if the project already has an existing database.
In my everyday life as technology leader ("tech lead") and full stack developer I run into a lot of problems that need to be solved every day.