Salesforce Architects whether they be Solution Architects, Technical Architects or some other type of Architect should have at least a good working knowledge of how to code.
Documenting a Salesforce Org is really challenging because it can be complex especially when working across many different branches or divisions. Maintaining and keeping the documentation in sync is also really difficult if there isn’t significant executive sponsorship.
In this blog article, we’ll be focused in on the Analytics API because it’s primarily used for reporting and dashboards.
In this post, I show my favourite library.
Where possible we should really be trying to use Lightning Web Components over Visualforce. The main reason we should prioritize Lightning Web Components over Visualforce is because of a lot of the out-of-the-box benefits: more modern, more responsive, and frankly, Visualforce will at some point be deprecated.
Visualforce is still useful though, here are some good situations to consider still using it:
- Building Wizards (multi-step processes)
- Needing to control the flow through an application.
- Org isn’t using Lightning yet (this should be really rare in 2021)
Apex isn’t going anywhere. For the most part, Lightning Web Components will need to call Apex code if you are doing anything really custom. The Lighning Data Service is pretty good, but it’s not going to work in every circumstance.
Wrapping it Up
Visualforce is slowly disappearing; there are very few situations that mean we should start new pages or Visualforce components with it.
Apex isn’t going anywhere.
Most governor limit errors are a result of poorly understanding how Salesforce works, so they can be prevented by designing a better architecture and by taking advantage of the platform. For example, too many SOQL queries can be avoided by writing bulk-friendly code or using caching.
Batch Apex has some incredible advantages over regular apex. The execution time of batch apex can be much longer and a lot more records can be processed. Scheduling Batch Apex has even more benefits than batch apex: it can do large jobs regularly.
Over time, Salesforce orgs get more and more complicated especially when a consultant, admin or developer leaves the organization with their knowledge of the system.
On Salesforce, if you want to process thousands of records the only way to truly achieve it is through asynchronous apex.
In this blog post, we cover the various ways of doing Asynchronous Apex.
Security in Salesforce and on the Force.com platform can be really hard to understand. In this blog post, we’re going to have a look at the “With Sharing” and “Without Sharing” Apex keywords.
In Salesforce, the Standard Query Language (SQL) didn’t have a great way of doing SELECT * or select all fields but that changed in Spring 2021.
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.
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.