We all are well aware about PageLayout and Visualforce Pages. From API 29 (Winter 14 release), Salesforce has introduced new functionality in platform named “FlexiPage”. Like Pagelayout, We can add Custom components in Flexipage however Flexipage will be visible only in Salesforce1 application in sidebar.

We can use Flexipage to make custom Homepage for some product which will be accessed directly from Salesforce1. One important thing to note here is that, till date (at the time of writing this tutorial) Flexipage can be defined in XML file and then deploying it using Eclipse, Ant Migration tool, workbench or any other migration tool. There is no way to define Flexipage directly in Salesforce using point and click functionality.

Flexi page can contain List View, Recent Items, Report chart, Visualforce page and Global actions.

Update 8-July – Flexipage is refered as “Lightning Page” in Salesforce documentation.

Step1 : Defining XML file for Flexipage containing detail of components

Filename – “AccountFlexi.flexipage”

<?xml version="1.0" encoding="UTF-8"?>
<FlexiPage xmlns="http://soap.sforce.com/2006/04/metadata">
  <flexiPageRegions>
    <componentInstances>
      <componentInstanceProperties>
        <name>entityName</name>
        <value>Account</value>
      </componentInstanceProperties>
      <componentInstanceProperties>
        <name>filterName</name>
        <value>AllAccounts</value>
      </componentInstanceProperties>
      <componentName>flexipage:filterListCard</componentName>
    </componentInstances>
    <name>main</name>
  </flexiPageRegions>
  <quickActionList>
    <quickActionListItems>
      <quickActionName>NewAccount</quickActionName>
    </quickActionListItems>
  </quickActionList>
  <masterLabel>My new App</masterLabel>
</FlexiPage>

XML file for Flexipage must needs to have “flexipage” extension and should be saved in “flexipages” folder.

Components supported in Lightning Page / Flexi Page

• flexipage:filterListCard
  • Points to a list view and displays the first few records from that view
• flexipage:recentItems
  • A list of most recently used items that supports these objects, based on the specified properties
• flexipage:reportChart
  • Use the Report Chart component to include a chart from a report in your Lightning Page
• flexipage:richText
  • Use the Rich Text component to add text and simple HTML markup to your Lightning Page
• flexipage:visualforcePage
  • Use the Visualforce Page component to include a Visualforce page in your Lightning Page

Note :

• For List View Supported objects include standard objects (Account, Campaign, Case, CollaborationGroup, Contact, Contract, Lead, LiveChatTranscript, Opportunity), custom objects.
• Recent Items are available only for Custom Objects.

Step 2 : Create package.xml

<?xml version="1.0" encoding="UTF-8"?>
<Package xmlns="http://soap.sforce.com/2006/04/metadata">
  <types>
    <members>AccountFlexi</members>
    <name>FlexiPage</name>
  </types>
  <version>29.0</version>
</Package>

Step3 : Deploying Flexipage

Create Zip file containing above both XML files. you can download it from here also.

We need to deploy this zip file into Salesforce and for that, I am going to use Workbench. In Workbench, navigate to deploy, select your zip file and select “Single package”. Once you have successfully deployed above zip file, you will see below page conforming Success message.

Step4 : Creating Tab for Flexipage

Once deployment is done, we can create a new Tab for flexipage. Navigate to create new Tab and at bottom of page you will see option to select new tab for flexipage as shown in below image.

Now, go ahead and create a new tab by providing all necessary information. You should be able to see your flexipage in next screen which you just deployed in step 3.

Step 5 : Configuring Navigation menu in Salesforce1

After creating flexipage tab, We have to tell Salesforce1 engine to display this tab in navigation menu of salesforce 1.

Navigate to “Setup | Administration Setup | Mobile Administration | Mobile Navigation” and add Flexipage to navigation.

Step 6 : Testing Flexipage / Flexipage in Action
Now login to Salesforce application from your mobile phone by launching Salesforce1 app or you can also launch it from your browser by navigating to this address “https://YOURINSTANCE.salesforce.com/one/one.app”.

please provide feedback on this post if there is chance of making it better.

If we switch from Revenue to Quantity the Quota of user will show blank user. In this article we will upload User Quota in Quantity.

After Winter 14 release also salesforce has not provided any Out of the box tool to upload quota from User Interface. So in this article also, we will depend on Dataloader.

Important Note :

1. If you want to upload Quota in Quantity, version of Dataloader must be above 28. In this article, i have used DataLoader version 29.
2. At one time, we can either insert Quota in Amount or Quantity.
3. If you want to use field Product Family, you must enable “Forecasting for Product Family”

As seen in previous article, Object used for upload Quota is “ForecastingQuota” which will be visible in Dataloader, if we select “Show all Salesforce Object”.

You will find below fields available for mapping in Dataloader :

1. Start Date (Quota is for Which month ?)
2. Currency ISO Code (ISO Code of Currency of Amount)
3. Quota Amount (Quota of users in Amount)
4. Quota OwnerId (Quota belongs to Which User ?)
5. Product Family (If Forecasting for Product (Winter 14) is enabled then you can use it)
6. Quota Quantity (Quota of users in Unit)

We have to create CSV file, map field and insert. I hope this tutorial will explain all you need to upload Quota in Quantity.

Please find below Sample csv files to upload Quota in Collaborative Forecasting :

1. Sample CSV FIle for ForecastQuota in Amount
2. Sample CSV file for ForecastQuota in Unit with Product Family
3. Sample CSV File for ForecastQuota in Unit Without Product Family

161 : Sometimes while deleting record it gives error “Object cannot be Deleted”. What is the reason for this kind of error ?
Ans :
This is generic error message prompted by Salesforce many times, which is not well informative. To get informative message, we can try to delete same record in “Developer Console”. In Developer Console Debug log, we will get exact error message.
Example : Lets say there is one record which is parent of more than 2000 records and grand parent of 5000 records. In such scenario from developer console it gives error something like “record cannot be deleted because it has many associated objects” However in User Interface, it will just display that “Object cannot be deleted.“

162 : Why are Visualforce pages served from a different domain?
Ans :
If we see carefully, all our Visualforce pages are served like “c.YOURSERVER.visual.force.com/apex/YOURPAGENAME” ,
And because of this most of time we run into Same-Origin Policy error in Javascripyt if we try to access parent page from Iframe. Following reason is explained by one of the evangelist of Salesforce:

“The move to separate domains has one very specific purpose: leverage the browser security model (same domain policy) to protect our customers and the salesforce.com service from cross site scripting and cross site request forgery attacks.

Moving to the serving pages from separate domains is a critical component of our ongoing commitment to insure the highest level of security and availability for everyone.

In the world where everything is served from the same domain any custom page that you visit had full access to any other page in your org and also any page served from salesforce.com itself. This included potentially malicious code that was installed as part of a force.com package.”

163 : In below code snippet , What is your observation and what is going wrong ?

trigger TestBeforeDelete on Lead (before Delete) {

        for(Lead l : Trigger.Old)
        {
            l.addError('error');
        }

        String msgBody = 'Test Email';
        String Subject = 'Test from Cogni Force on Lead';
        Messaging.SingleEmailMessage mail = new Messaging.SingleEmailMessage();
        String[] toAddresses = new String[] {'abc@gmail.com'};
        mail.setToAddresses(toAddresses);
        mail.setReplyTo('abc@gmail.com');
        mail.setSenderDisplayName('Cogniforce Test Simulator');
        mail.setSubject(Subject);
        mail.setPlainTextBody(msgBody);
        mail.setHTMLBody(msgBody);
        Messaging.sendEmail(new Messaging.SingleEmailMessage[] { mail });
}

Ans :
It will not send any email. Because “adderror” prevents all transactions from committing including emails.

164. Can we mass delete reports using Apex (Anonymous Apex) ?
Ans :
Salesforce has not exposed any API for Reports. So best way is :

1. Move all reports needs to delete in new folder.
2. Inform everyone that reports will be deleted after some time may be 30 days.
3. Import your reports folder in Eclipse including all reports to be deleted and then delete the the reports folder in eclipse. It will delete all the reports at once.

165. While creating Dynamic SOQL, which involves Datetime gives ” no viable alternative at character ‘<EOF>’ ” error.
OR
value of filter criterion for field ‘CreatedDate’ must be of type dateTime and should not be enclosed in quotes
OR
How to use Datetime in Dynamic SOQL Query in Salesforce ?

Ans :
This error is because of wrong construction of Dynamic Query with Datetime. following code snippet will give idea on how to construct dynamic query for Datetime ?

//format the datetime to make it Dynamic Soql ready
String formatedDt = cutOffDateTime.format('yyyy-MM-dd'T'HH:mm:ss'Z'');
String sql = 'SELECT  a.Id  FROM  Agents_Answer__c a    WHERE  a.Agents_Test_Result__r.Agent_Name__r.IsActive__c = false AND  LastModifiedDate < '+ formatedDt ;

Where, “cutOffDateTime” is variable of datetime type.

166. How you can use Datetime field as a criteria in SOQL Query ?
Ans :
We cannot use Datetime as condition in Where Clause in between single Quotes.
You can do something like this ,

WHERE CreatedDate > 2005-10-08T00:00:00Z

Or, you can also use Date Literals like

WHERE CreatedDate > YESTERDAY

For more information on date formats and more literal values, check this URL.

167. After Data Export using DataLoader, Some time it appears that data is on New Line (Carriage Return) when we open CSV file in Microsoft Excel. For example , Address Data separated on different lines. How can we override this problem ?
Ans :
Excel does all sorts of “useful” things when it opens a CSV file. It will re-format dates, strip leading zeros, corrupt record IDs (if you have them in your report), and as explained it will also break line. Best way as per my experience till date is, Upload document to Google Drive. Export document back from Google drive as Excel.

Please post comment in this article if you know any other working way.

168. How do you import Converted Lead into Salesforce from Legacy System ?
Ans :
Fields we need for importing converted leads are “ISCONVERTED” , “CONVERTEDCONTACTID” , “CONVERTEDOPPORTUNITYID” and “CONVERTEDACCOUNTID“.
Step 1 : As above fields are not editable, we have to contact Salesforce Support to enable Audit fields. Enabling Audit fields means we can edit few Readonly fields like created date and above lead fields.
Step 2 : Import Account, Contact and Opportunity from Legacy system to Salesforce.
Step 3 : If you imported account, contact and opportunity in Step 2, Salesforce automatically generates Unique ID. We need that unique Id to insert Converted Lead. So Export Account, Contact and Opportunity, which is inserted in Step 2 from legacy System.
Step 4 : Create CSV File with All lead information with ISCONVERTED=TRUE and CONVERTEDCONTACTID, CONVERTEDOPPORTUNITYID, CONVERTEDACCOUNTID. CONVERTEDCONTACTID, CONVERTEDOPPORTUNITYID and CONVERTEDACCOUNTID should correspond to Ids generated by Salesforce for Contact, Opportunity and Account which will be related to converted lead.
Step 5 : Once CSV is properly created with all required Data, Insert it using DataLoader.

Note : We cannot convert existing lead using this process. Leads must be inserted with these four fields. If you try to update lead it will not give you option to edit above fields.

169. How to setup Field Level Security (FLS) for Person Account Fields.
OR
Why I am not able to find list of Person Account fields in Field Level Security (FLS) settings when navigated to fields on Account Object.
Ans :

Field Level Security (FLS) of Person Account fields ar controlled by Contact Fields. So, if you want to setup FLS of Person Account Fields navigate to fields of Contact and it will be reflected on Person Account.

170. In Partner Community, external user is having appropriate OWD and Profile Settings for Opportunity or consider any other Object. However they are getting insufficient privilege access, what might be cause of this error ?
Ans :

• Check External User has all FLS for fields used in Report Filters
• After Winter 14, If Community enabled, there will be two kind of OWD. External and Internal means what information should be visible to internal and external users. Also , there will be new setting named “Standard Report Visibility“. If it is checked user can see reports based on Standard report type even though they don’t have proper OWD and may expose sensitive information about internal user to external users (for example : Internal users role). If external user is getting an error whole running the report this setting may be one of the cause.

Major Area of Release:

• Developer Console
• Canvas
• HTML5 Support in Visualforce
• Deployment related features like improved deployment Monitoring
• New Database methods to get records deleted , updated in specific time

Renaming

• “Service Cloud Console“ is renamed to “Salesforce Console for Service“
• “Configuration Only“ sandbox renamed to “Developer Pro“
• “Agent Configuration“ renamed to “Live Agent Configuration“

1. Add Report Charts in Detail Page Layout of Standard or Custom Object

Starting from Winter 14, Now we have one more option in Page Layout Editor, which is “Report Charts”. Instead of Visiting Dashboard and Report we can see chart right in Detail page of record.

Considerations:

• You can have two report charts only per page.
• Report chart can only be added from enhanced page layout and is not supported in mini Console or original page layout editor.

2. Get Report Data as JSON – Analytics API
This is REST based API which will return data of report as JSON. This will revolutionize the way we access and visualize Salesforce data.

3. Search Metadata
One of my favorite features is searching Metadata. We have Global search which will search any record. But what if you have more than 200 Workflow rules, Email templates and struggling to find out what you need? You must be thinking for search feature which can search your setup, and this feature is available from Winter 14.

4. Static Resource Editors just inside Developer Console
Developer Console editor now supports JavaScript, XML, CSS and plain text. You can create these file in Static Resource just from Developer Console.

5. OFFSET in SubQuery – Pilot
OffSet is very useful clause in SOQL for pagination however it can only be used in upper level query. From Winter 14 (Pilot) it can be used in sub query also.

SELECT Name, Id
(
SELECT Name FROM Opportunities LIMIT 10 OFFSET 2
)
FROM Account
ORDER BY NAME
LIMIT 1

6. Lookup field search
Till now Lookup field can only search Name field however now we have option to “search All” Fields.

7. Sales Console
It helps you quickly contact leads, access companies, and identify key contacts – all in dashboard like interface.

8. Freeze User Accounts
We can now temporarily suspend a user account that requires more work to deactivate.

9. Sharing rule on User

You might be thinking that what Is use of having OWD and sharing rule on User ? As chatter is getting adapted by everyone, there may be scenario that few profiles should be private like of CEO. So in those case we can create sharing rule on User records.

10. Manager Group
When it comes to sharing we know OWD, Role and Sharing rule. Now start assuming one more level which is “Manager Group”. The role hierarchy controls the level of visibility that users have into your organizations data. With Winter’14, you can use manager groups to share records with your management chain, instead of all managers in the same role based on the role hierarchy.

11. Flexible API Limits – Pilot

Flexible limits allow your organization to exceed its API request limit up to 50 percent above your normal limits within the limit timeframe (typically 24 hours). For example, if your daily limit for API requests is 100,000, it’s extended to 150,000. The following day, if your organization activity spikes again, the limit will be extended to 150,000 requests again.

12. Server Side View State – Pilot

Server-side view state maintains a Visualforce page’s view state on the server, instead of sending it back and forth during form submissions and responses. This can reduce the amount of data being transmitted per request, which can improve performance, especially over connections with limited bandwidth or high latency, such as a mobile wireless connection.

13. Statement Limit Elimination from Apex

The code statement limit has been removed. Apex transactions are no longer limited by the number of code statements they can execute, allowing you to potentially execute more code statements than the previously enforced statement limit. To protect against infinite processes overusing shared CPU resources, the maximum CPU time for a transaction is 10,000 milliseconds for synchronous Apex, and 60,000 milliseconds for asynchronous Apex (Batch Apex and future methods).