Reasons why the Salesforce Project Fails? This post doesn’t intend to depress or discourage you; rather, it focuses on disaster risk reduction and how to reduce it. According to the risk factor’s severity, I have divided my groupings into three parts — High, Medium, and Low. Salesforce has grown in the last 2 decades massively. It has given the business one of the state of its art CRM tool which has changed the way of doing business. Across the planet, industries, companies, and individuals are using & recommending Salesforce. Salesforce is leading the charts in Gartner Magic Quadrant for the last 5 years continuously. Did you realize that as many as 70% of CRM projects end in failure ? If you’re intending to use a CRM solution like Salesforce for the first time, this could sound disheartening. The good news about failure is that we can grow from it. I’m about to discuss the main causes of implementation failure and how to steer clear of each one. HIGH-RISK FACTOR...
Popular posts from this blog
Best Practice to write Apex Triggers in Salesforce 1)One Trigger Per Object A single Apex Trigger is all you need for one particular object. If you develop multiple Triggers for a single object, you have no way of controlling the order of execution if those Triggers can run in the same contexts 2) Logic-less Triggers If you write methods in your Triggers, those can’t be exposed for test purposes. You also can’t expose logic to be re-used anywhere else in your org. 3) Context-Specific Handler Methods Create context-specific handler methods in Trigger handlers 4) Bulkify your Code Bulkifying Apex code refers to the concept of making sure the code properly handles more than one record at a time. 5) Avoid SOQL Queries or DML statements inside FOR Loops An individual Apex request gets a maximum of 100 SOQL queries before exceeding that governor limit. So if this trigger is invoked by a batch of more than 100 Account records, the governor limit will throw a runtime exception 6) Us...
Comments
Post a Comment