Skip to main content

Ext JS 4 – Set custom idProperty for DataStore when fields are given

In EXT JS 4 there still is a chance to pass only the fields and data directly to the DataStore when you construct it, instead of passing a model. Ext JS is then creating an internal model from the fields passed. Now, the problem is that Ext JS is going to append an identifier field ‘id’, if there is no field given with that name. If our identifier field has other name, like ‘customID’, then it causes a lot of trouble when it comes to getting the record with a given identifier (getById). Unfortunately there is no way to specify which field we’d like to use as identifier in this case.
I have come up with the following solution: I am building a temporary model on-the-fly from the fields. On this model I am able to specify which field I would like to use as identifier. Here is my method for creating a DataStore from the given fields and columns. You may notice, that in case the idProperty is not set, I am using the first column as identifier.



createDataStore : function(fields, data, idProperty)
{
    var dataStore = Ext.create('Ext.data.ArrayStore', {
        model : Ext.define('info.lacyg.extjs.GenericModel' + Ext.id(), {
            extend : 'Ext.data.Model',
            fields : fields,
            idProperty : idProperty || fields[0].name
        }),
        data : data
    });

    return dataStore;
}

Comments

Post a Comment

Popular posts from this blog

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 4 with Spring MVC Example

Introduction When developing a brand new application for the company I work for, one of the first thing I implement is "authentication". Not only is this process generally a prerequisite to access many other functions but it is also very simple and covers every layer of an application, from GUI to the database. So instead of another minimalistic "Hello World" tutorial, here is a "Login/Password" example, using 2 famous technologies : Spring MVC and ExtJS 4.   Prerequisites Because this tutorial is quite long, I won't go into the details of each technology I used but I will mainly focus on how ExtJS and Spring can be nicely used together. So here are the things you should know before continuing : Spring framework (good knowledge) Spring MVC (basic knowledge. See  Spring MVC Official Documentation  for details) ExtJS "application architecture" (see  Sencha Docs  for details) Eclipse IDE + Tomcat 6 (or any other web container) You a...

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 ( ...