Salesforce: Some Insights

Much has been written and presented around Salesforce single organisation and multi-organisation strategies. But, still the question is asked quite frequently. There are really good articles and blogs and I'm hereby trying to compile the information and add my views to it, to provide a summary. Single Org. Approach In a single org. approach, an organisation maintains one single Salesforce org. all their required operations (planned to be executed via Salesforce) are executed via same org. Ideal for: Small and Medium Businesses Pros Less environment maintenance overhead Uniform processes - a very good opportunity for organisations which want to implement uniform processes/ functionalities across all units Easier user provisioning - once a user is setup, they have access to required functionalities Cons Complicated processes as organisation grows larger and include various operations/ geographies Increased application conflicts - with same processes being used...

How many of you have faced problems understanding the basic difference between Object relationships (as provided by Salesforce.com) and Table/entity Relationships (as provided in conventional RDBMS)? I am sure many of you must have faced the same problem, at least I did. But lately there are some new enhancements in SOQL which narrows down these differences. For e.g now in SOQL you can have INNER JOINS and you can group data using the famous GROUP BY clause. So, what is the big deal? Well, yeah it’s not a big deal that you can - do more in SOQL and remove your earlier code using which you used to retrieve data in case of INNER JOINS or - group your data using GROUP BY clause and have conditions on it using HAVING clause or - use some new Date functions in your SOQL query to filter your data (which you used to do using Apex code). So, in all it means richer SOQL and lesser use of Apex for these purposes. Interested, then checkout a very good article written by Dr. Umit Ya...