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.
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.
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.
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.
Salesforce orgs tend to become cluttered with technical debt and functionality that is no longer being used. The longer the technical debt and unused functionality is allowed to exist the more expensive it becomes because of confusion, complexity, and potential project delays.
In this blog post, we have a look at how to identify technical debt and how to begin removing it.
Up until recently, if you were building websites you pretty much always used jQuery. jQuery really simplified working with the browser document object model (DOM) and doing really custom animations.
In this blog post, we go through how to jQuery with the Lightning Locker Service turned on.
When building a database it’s so important to build the right relationships between database tables. What this means is that when we’re creating relationships between objects is that we’re deciding how they will be associated with one another. Salesforce has a very similar concept, which shouldn’t really be a surprise considering there’s a database powering the entire thing!
Once you know how to do it, getting the current Record Id in a lightning component or lightning aura component is pretty easy. We simply need to implement the force:hasRecordId interface in the lightning component.
The lightning:recordEditForm allows us to create a custom looking form that can interact with Salesforce records, or create new Salesforce records.
In this blog post, we’ll go over how to create a custom submit button for a lightning:recordEditForm
Lightning Data Service is a game changer for Salesforce Developers and Lightning Components (Aura) because it reduces the amount of work required by developers.
Implementing CRMS like Salesforce into an existing company can be really challenging if users aren’t interested in using it or resistant to change. I recall the first time I integrated Salesforce into an organization, we had a very difficult time getting the sales staff to actually use it. Eventually we found a way to get staff interested in using the CRM and stop using Google Docs or Excel sheets.
It’s no secret that Salesforce Lightning is changing the way we develop for Salesforce. At Dreamforce 2014, Salesforce introduced Salesforce Lightning and it is proving to change a lot of things we do on the platform and I’m sure it will make things a lot better for users in the long term. If you aren’t already familiar with Salesforce Lightning then you need to read my post called What is Salesforce Lightning. Continue reading