Visualforce component is not supported- Issue resolution on Force.com platform

Hi,

This blog post deals with common error thrown BY Force.com: is not supported.

You can raise a case from Salesforce.com partner portal for enabling Dynamic visualforce component in your organization under "Feature Activation" item for case. Salesforce.com team will ask for OrgID for doing so. So it would be quick if you could provide your OrgID while raising the request asking like "I want to enable dynamic visualforce component in my org with orgID:". They will enable within 1 working day( based on my experience).

If you have already enabled the dynamic visualforce components feature in your Salesforce.com organization and still getting this error, then the problem lies with version number of Visualforce page.

I came across such situation where even after enabling this feature I used to get such message. On analysis I found that the root cause was VF page version number:

You get such error in this case: If you are navigating from a VF page whose version number 18 to a VF page whose version number is 24. Since version 18 doesn't support dynamic visualforce components, so when Force.com runtime engine is navigating user from a page (v18 ) to page (v24) it somehow doesn' t take into account the version number of target page i.e. 24 and assumes version of target page as 18 and thus throws such error.

I hope this post will help you to resolve this issue.

Cheers !

Salesforce's Force.com SaaS Platform

We all might be aware of Salesforce.com because of its CRM. The global market leader in Cloud Computing is leaving its mark in the industry by providing powerful tools to internet users. One such platform salesforce.com is providing is Force.com. It is based on the same MVC(Model-View-Controller) paradigm as in Java based WebApps. It is basically a PaaS (Platform as a Service) company making huge efforts to hold its position in the cloud league.Force.com is the place where you can develop cloud application that will reside on the salesforce' data-centers. They want all of developers to concentrate on business logic to be implemented rather than the maintenance and administration of resources leveraged.

A Force.com application basically comprises of set of tabs, visualforce pages, workflows, approval processes, triggers and controllers containing business logic. We can develop Application in two ways: Declarative and Programmatic approach. In declerative we develop Apps with clicks whereas in programmatic we code everything. Best of the Apps will include mixture of both approaches.

Considering each component under MVC approach, First is Model. Model is basically abstraction layer between actual salesforce's databases and controllers(business logic). Model is composed of set of objects(Salesforce paradigm). You will have set of standard objects, which will be required for any enterprise App. You can create web pages known as VisualForce pages which are rendered as HTML on server for each HTTP request. Pages. Visualforce pages are  developed using Apex page tags. These are similar to HTML tags but with some special attributes and new element library specific to Force.com. Business logic for Apps is written in a controller. A controller is basically a class which controls the functionality of the page associated with it. The controller code is written in Apex language. It is a force.com specific cloud app development language. Controller has got instance variable, constructors, methods similar to that we do in Java. These methods and variables are bind to page controllers using merge fields. Suppose there is a instance variable "UserName" we will bind it to the page component like: <apex:outputField value='{!<objectName>.UserName}'/>

For more details on Force.com :

Apex: http://www.salesforce.com/us/developer/docs/apexcode/salesforce_apex_language_reference.pdf

VisualForce: http://www.salesforce.com/us/developer/docs/pages/salesforce_pages_developers_guide.pdf