hi trent,

i think it's as simple as changing the editable property on your store and/or editorgrid. it probably gets set when the store loads, but you could listen for that even and change it. you could add your column at this point too.

if you want to get more involved, look at what ehrStore.js does in the EHR module. That extends the labkey store. the onProxyLoad method listens for when the query metadata is returned by the server. at this point you can modify or augment it. it's a pretty low level way to hook into things.

out of curiosity, what's the point of editing 1 column if it isnt going to be submitted?

Thanks. Well I took a look at the store documentation, and there is one config option updatable, so I tried setting that to true (and after checking, it defaults to true anyways); And I also have editable specified as true in the instantiation of the editorgridpanel.

But I'll take a look in the ehrStore.js - that might give me some more clues, thanks.

… just trying out an idea; I found some code to export a grid to XLS format. So seeing if we can get the specimen repo working this way; the requests work by clients requesting a specific vial size, which I don't think the built in specimen repo supports.

you know i think the labkey editorgridpanel has a columnModelCustomize event (or something similar). i believe the way you are supposed to manipulate column in that grid is to listen for that event (which is async since the store must load data from the server) and then modify the columns array it returns. that would allow you to all the column, but you may run into a problem downstream because that column wouldnt actually exist in the store. if this does work though it's easier and requires knowing less about the guts of ext.

hooking into the store as i mentioned above is a step upstream of the EditorGridPanel's columnModelCustomize event. it's more work to get it working (although not that much work), but might be more robust.

ah right. cool.

just thinking about it, i think i may be looking at this wrong. There are obviously events that take place after editing a column value to update the store, which is why its preventing the columns being editable.

I might be better of just calling the selectRows function and creating an ArrayStore based on the returned data.

hi trey,

a few other comments:

1. how are you debugging this?

2. the array store thing is probably feasible, but i think you'll find simpler and more robust approaches. i pretty much never use selectRows() for anything these days since passing your data through a store is just much better. it does take some wrapping your head around it though. if you plan to do anything along these lines in the future, i'd suggest taking a little time on this.

3. i saw you mentioned grid -> excel. i dont know what route you were thinking of using, but while the labkey store supports exporting to excel, it appears to be tied to the underlying SQL query, rather than the records in the client-side store. therefore if you're adding values on the client that wont be reflected. however, LABKEY.Utils.convertToExcel can do this. on the client you'd iterate over your store's records, build an excel object and then use this API to return an excel file.

1. As you may have noticed, I use console.log a bit. I use chrome, so just use the dev tools included.

2. Ok, I took a better look at the customizecolumnmodel event - actually the documentation provides an example of using it.

However, even if I update the field in the event, it still doesn't become updatable. (I try updating the sortable field there, and that does get affected - it's just the editable that doesn't).

In the example they provide, they call a custom renderer function, so thought maybe something is in there:

function newTest(columnModel, index){
       if (columnModel != undefined){
           console.log(index.vol.editable);
           i = index.vol;
           i.sortable = false;
           i.renderer = newRenderer;
           index.vol.editable = true;
           console.log(index.vol.editable);
       }
   }

function newRenderer(data, cellMetaData, record, rowIndex, colIndex, store){
       console.log('*******');
       console.log(data);
       console.log(cellMetaData);
       console.log(record);
       console.log(rowIndex);
       console.log(colIndex);
       console.log(store);
   }

If I inspect record, the store object has a property of updatable which is set to true, which add to the confusion.

3. I was looking at this code: http://www.sencha.com/forum/showthread.php?32400-GridPanel-directly-to-Excel … but just now I thought I better test it to make sure it actually works. Unfortunately it looks like there are some server side validation that don't like some of the values in the script. So I may have to look for another solution.

Thanks for all your help and advice.. appreciate it :)

Just as a side note for anyone that may be interested. That script I found on Sencha isn't even necessary as I was trolling through the LabKey Javascript API doco, and found this:

https://www.labkey.org/download/clientapi_docs/javascript-api/symbols/LABKEY.Utils.html#.convertToExcel

Which returns an Excel spreadsheet based on the JSON data sent through. Very cool!