{"id":3706,"date":"2014-02-16T13:36:15","date_gmt":"2014-02-16T08:06:15","guid":{"rendered":"http:\/\/JitendraZaa.com\/blog\/?p=3706"},"modified":"2014-03-31T05:43:16","modified_gmt":"2014-03-31T05:43:16","slug":"introduction-to-visualforce-remote-objects","status":"publish","type":"post","link":"https:\/\/www.jitendrazaa.com\/blog\/salesforce\/visualforce\/introduction-to-visualforce-remote-objects\/","title":{"rendered":"Visualforce Remote Objects"},"content":{"rendered":"

One of the exciting feature of Spring14 release is introduction of “Visualforce Remote Objects”. You can say its actually replacement of JavaScript Remoting<\/a>.<\/p>\n

Why do we need “Visualforce Remote Objects” when we already have “JavaScript Remoting” ?<\/strong><\/p>\n

Well, here are few advantages of “Visualforce Remote Objects” :<\/p>\n

    \n
  1. No need to write Controllers, Everything can be done in Visualforce only.<\/li>\n
  2. As @RemoteAction<\/em> annotated methods needs to be static so you had to take special precaution as it didn’t supported Viewstate. This hurdle is completely removed now.<\/li>\n
  3. No need to write Test Class now, as no Controller is involved.<\/li>\n<\/ol>\n

    How to start with this ?<\/strong><\/p>\n

    At time of writing this article, This feature is under Pilot release. So, you have to contact Salesforce support to enable it in your Organization.<\/p>\n

    Visualforce code Sample :<\/p>\n

    \r\n<!-- This Demo will assume Querying Account Object -->\r\n<apex:remoteObjects>\r\n<apex:remoteObjectModel name="Account" jsShorthand="getActs" fields="Name,Id">\r\n <apex:remoteObjectField name="ClientType__c" jsShorthand="cType">\r\n<\/apex:remoteObjectModel>\r\n<\/apex:remoteObjects>\r\n<\/pre>\n
    you can see in above code, few new Visualforce tags are introduced like “remoteObjectModel<\/em>” and “remoteObjectField<\/em>“.<\/p>\n
    jsShorthand<\/em> attribute defines shortcut that can be used inside your JavaScript code. Now, we don’t have to write annoying object or field name ending with “__c” or namespace name. This will keep our code tidy.<\/p>\n
    Javascript code Sample :<\/p>\n
    \r\n\/\/Create new Remote Object Reference\r\nvar src = new SObjectModel.getActs();\r\n\r\n\/\/Use Remote Object to query 5 records\r\nsrc.retrieve({\r\n\t\t\tlimit : 10,\r\n\t\t\twhere : {\r\n\t\t\t\tcType :{\r\n\t\t\t\t\teq : 'Banking'\r\n\t\t\t\t\t}\r\n\t\t\t}\r\n\t\t} ,\r\n\t\tfunction(err,records){\r\n\t\t\tif(err == null)\r\n\t\t\t{\r\n\t\t\t\t\/\/Process returned "records" to display in Visualforce code.\r\n\t\t\t}\r\n} );\r\n<\/pre>\n
    In above code, we are calling retrieve()<\/em> method of Javascript object SObjectModel<\/em>. Once you get records, you can process it in your javascript. Other than retrieve()<\/em> , you can perform all CRUD operations on object.<\/p>\n
    You can see below articles also on same topic.<\/p>\n