Solution: You probably have an Apex Class with the same name already. Check the name of your apex class and modify accordingly.

string test='edwin.vijay.raymond';
system.debug('***'+test.countMatches('.'));

OUTPUT: 2

ISSUE:
I created a Salesforce Community, tried to edit the community using Site.com Studio and could not find a way to add DATA and form elements. This is how my editor looked like.


RESOLUTION:
Change the template to 'Salesforce TABS + Visualforce' and the DATA and FORM elements will be available. The DATA and FORM elements are not available/visible with the Kokua, Koa, Napili and Aloha templates.

If you have already created pages with any of these templates, you will have to delete ALL pages and then change the template to 'Salesforce TABS + Visualforce'. Any new page you create after this will have the DATA and FORM page elements.

Salesforce Official Help link: Click here

Use the following piece of code to submit approval requests in BULK. This code can be anonymously executed from the developer console.

<apex:page showHeader="false">
<style>
a.msglink{
 font-size: 100% !important;
 margin: 0 3px !important;
 color: #015ba7 !important;
}
</style>
 <apex:outputpanel rendered="{!$User.IsDowngrade__c}" style="margin:0 3px !important;font-sixe:100% important;">
  <apex:pageMessage severity="info" strength="3" summary="This is a test message. Please<a href=https://www.google.com class=msglink target=_blank>click here</a>to test." title="Link Notification" escape="false">      
  </apex:pageMessage>    
 </apex:outputpanel> 
</apex:page>

Note the following:

• escape="false"

• href=https://www.google.com and NOT href="https://www.google.com" 

• class=msglink to add style definitions

Salesforce has an out-of-the box setting to allow skipping validation rules when you CONVERT a Lead.

However, this setting is not available by default if your organization was created sometime before 2010 i believe. You could however, raise a case with Salesforce and they will enable the feature for your i both your production and sandbox instances.

Below is a screenshot of how it looks, if you do not see this option please contact Salesforce customer support and get it enabled.

Trigger

Apex Class:

The system throws a compile error : Method does not exist or incorrect signature even though everything seems correct. This is because the methods should be defined as static. Below is the corrected code. SOLUTION:

With Reporting Snapshots, you might come across this error message.




When you click into the row, it shows you the list of fields that have not been mapped properly.

Solution:
Check your mappings and the data type between the source and target fields. If that still does not solve the issue, check that the RUNNING USER has access to the source and target fields.

In this case, the 'Admin User' did not have access to the source fields and hence this error message.