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.
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.
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.
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.
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.
One of the most beautiful things of the Salesforce platform is that almost everything can be queried. Lightning components can be queried pretty easily.
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 record edit form is a really great new addition to Salesforce Lightning. The lighting record edit form is a wrapper component that accepts a recordId and can display fields and labels associated to that record.
Implementing Customer Relationship Management (CRM) software is vital to growing a company’s business because having a relationship with customers is vital. In this post, I will detail how to use crm to grow your business by implementing it correctly, making sure staff are using it and providing a few really good tips to automate business processes which will help reduce costs and drive revenue.…
In Apex, there’s quite a few constraints that are strictly enforced because the platform is a shared multitenant environment. Quite a few of the limits result in runtime exceptions that can’t be handled.
For those familiar with Salesforce, it’s no secret that there’s a lot of limits. For example, there’s limits around the ViewState which were pretty painful to work around.
One of the first limits, I believe all new Salesforce developers hit is the limit for a maximum of SOQL queries that can be done.…
At Dreamforce 2014, Salesforce announced they were changing the Salesforce User Interface to make it simpler to use. The new User Interface is called Salesforce Lightning. In my blog post, What is Salesforce Lightning I cover a lot more about what it is and how development differs from using Apex and Visualforce.
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.…
In the days of early computing, it was rare that companies would have a way of communicating with their customers that would scale as the company grew. Everything went into different “data silos” that wasn’t necessarily accessible to the right person at the right moment. When I started my career, I worked on phone systems that were mostly being used by mortgage brokers that usually worked off of lists of potential customers in excel.
Usually the brokers had no insight into how things were going or would go unless they kept adding columns for notes each time they called or emailed the person. If the mortgage broker worked on a team or had a manager – it was nearly impossible to coordinate how things were going because everything was based off of the data or papers even that one employee would keep on their computer or on their desk.
What is a Third Party Library