Skip to main content

Integrating Ext JS Combo Boxes with SalesForce.com

To integrate an Ext JS 4 UI with SalesForce.com and have run into a number of interesting challenges.
One of the issues that we ran into pertains to how remote Ext JS 4 combo boxes transmit query data to the back-end in order to perform incremental searches. Out of the box, whatever the user types into the combo box is transmitted over the uri, e.g. getmydata.aspx?query=somethingITypedIntoAComboBox. The problem is that the salesforce transport mechanism that we’re using only carries forward data passed in the http header, ignoring everything passed on the url.
We wound up modifying the combo box to transmit query data over a Store’s proxy header by setting up a combo box listener that dynamically changed the related store’s proxy header as illustrated below:
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
{
 xtype: 'combo',
 listeners: {
   beforequery: function(queryPlan,eopts) {
       this.store.on('beforeload', function(store,operations,eopts) {
          Ext.apply(store.proxy.headers, {
                      query:queryPlan.query
          });
       });
   },
   afterquery: function(queryPlan,eopts) {
      this.store.un('beforeload');
      store.proxy.headers.query=null;
   }
 },
 store: s,
 displayField: 'Name',
 valueField: 'Id',
 typeAhead: false,
 hideLabel: true,
 hideTrigger:true,
 anchor: '100%',
 listConfig: {
  loadingText: 'Searching...',
  emptyText: 'No matching posts found.',
 
  // Custom rendering template for each item
  getInnerTpl: function() {
    return '

{Name}

'
;
  }
 },
 pageSize: 10
}
The underlying Store used the SalesForce.com services proxy:
1
2
3
4
5
6
7
8
9
10
11
12
13
14
Ext.define('MyApp.store.MyStore', {
 extend: 'Ext.data.Store',
 storeId: 'MyStore',
 idProperty: 'Id',
 fields: [ { name: 'Id' } , {name: 'Name'}, {name: 'BillingCity'}],
 proxy: {
   type: 'rest',
   url: '/services/proxy',
   headers: {
     'SalesforceProxy-Endpoint' :  serverURL + PATH,
     'Authorization': 'OAuth ' + SESSION_ID
   }
 }
});
The serverUrl and session ID are dynamically output at runtime from SalesForce’s apex architecture:
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
<apex:page docType="html-5.0" sidebar="false" showHeader="false"
    standardStylesheets="false" cache="true" applyBodyTag="false">
  
<html lang="en">
  <head>
    <meta charset="utf-8"/>
    <script src="{!URLFOR($Resource.ExtJS,'ext-all.js')}"></script>
    <link rel="stylesheet" href="{!URLFOR($Resource.ExtJS,'ext-theme-neptune-all.css')}"/>
    <script type="text/javascript">
      var SESSION_ID = '{!$Api.Session_ID}';
      var serverURL = '{!SUBSTITUTE(SUBSTITUTE(LEFT($Api.Partner_Server_URL_210, FIND( '/services', $Api.Partner_Server_URL_260)), 'visual.force', 'salesforce'), 'c.', '')}';
      // If its a mydomain enabled org, the mydomain name needs to be stripped
      var splitURL = serverURL.split(/\./g);
      if(splitURL.length==4) {
          splitURL[0] = 'https://';
          serverURL = splitURL.join(".").replace('.','');
      }
      
      var PATH = 'services/apexrest/XN/Account';
   </script>

Comments

Post a Comment

Popular posts from this blog

Ext4 Apply Store Filtering

In extjs4.1: There are many way for store filtering . Some of code i give here Filtering by single field: store . filter ( 'eyeColor' , 'Brown' );   Alternatively, if filters are configured with an  id , then existing filters store may be  replaced by new filters having the same  id . Filtering by single field: store . filter ( "email" , /\.com$/ );   Using multiple filters: store . filter ([ { property : "email" , value : /\.com$/ }, { filterFn : function ( item ) { return item . get ( "age" ) > 10 ; }} ]);   Using  Ext.util.Filter  instances instead of config objects (note that we need to specify the root config option in this case): store . filter ([ Ext . create ( ' Ext.util.Filter ' , {   property : "email" , value : /\.com$/ , root : 'data' }),   Ext . create ( ' Ext.util.Filter ' , {   filterFn : function ( item ) {   return item . get ( &

ExtJS - Grid panel features

What can we do with ExtJS GridPanel? I have to develop a lot of applications in my web app and I see that grid component of ExtJS may fit in. However, I am not aware of what all things I can do with the - off the shelf available framework pieces - available plug-ins in the marketplace and - custom development through my own developers This is a typical question that we hear from the business users who wants to design an application by keeping the framework’s capability in perspective. In this article I have tried to put the list of stuff you can do with grid and hopefully that shall enable you to take advantage of the beauty of ExtJS. Pre-requisites This article assumes that you are familiar with basics of ExtJS What are the available options? In this section I will be taking you through some of the commonly seen usage of ExtJS grid panel. While covering all the capabilities of grid may not be possible, I am sure it will be helpful for the business users who want to

EXTJS - Way to get a reference to the viewport from any controller

An easy way to get a reference to the viewport from any controller Here's an easy way to get a reference to your viewport from any controller: Ext.application({ launch: function(){ this.viewport = Ext.ComponentQuery.query('viewport')[0]; this.centerRegion = this.viewport.down('[region=center]'); } }); then, inside say, a controller, you can call this: this.application.viewport to get a reference to the viewport.