Hi Kelly, thanks. I'm bascially already doing the same thing wih a parcel - property 1:m (not showing require modules and aliases):
relGrid = new (declare([Grid, ColumnSet, DijitRegistry, ColumnResizer]))({
//minRowsPerPage: 500,
bufferRows : Infinity,
//selectionMode: "single",
loadingMessage: 'Loading data...',
noDataMessage : "No Records Available",
useTouchScroll: false,
columnSets : [
[
[
{field: 'ID', label: 'Account', resizable: false},
{field: 'LINK', label: 'Information', formatter : function(link) {return "<a target='_blank' href=" + link + ">Full Info</a>";}, resizable: false}
]
],[
[
{field: 'NAME1', label: 'Owner Name', resizable: false},
{field: 'JUST', label: 'Justified Value', formatter: toCurrency, resizable: false},
{field: 'ASSD', label: 'Assessed Value', formatter: toCurrency, resizable: false},
{field: 'YRBL', label: 'Year Built', resizable: false}
//{field: 'LSQFT', label: 'Recorded Area', resizable: false}
]
]
]
}, "divGrid");
//relGrid.startup();
function getLocation(evt) {
mapMain.graphics.clear();
mPoint = evt.mapPoint; //evt.
console.log(evt);
var queryParcels = new Query;
queryParcels.geometry = mPoint; //mPo
var parQuery = lyrParcels.selectFeatures(queryParcels,FeatureLayer.SELECTION_NEW); //deferred evacQuery
console.log(mPoint);
mapMain.infoWindow.setFeatures([parQuery]); //mapMain.infoWindow.setContent(evt.result.name);
mapMain.infoWindow.show(mPoint); ///evt.result.feature.geometry);
if (mPoint !== undefined) {
mapMain.centerAndZoom(mPoint, 13); //7 for sph mPoint 13
}
lyrParcels.on("selection-complete", findRelatedRecords);
function findRelatedRecords(event) {
features = event.features;
relatedParQuery = new RelationshipQuery();
relatedParQuery.outFields = ["OBJECTID","ID", "NAME1", "JUST", "ASSD", "YRBL", "LSQFT"];
relatedParQuery.relationshipId = 1;
relatedParQuery.objectIds = [features[0].attributes.OBJECTID];
lyrParcels.queryRelatedFeatures(relatedParQuery, function(relatedRecords) {
if (!relatedRecords.hasOwnProperty(features[0].attributes.OBJECTID) ) {
console.log("No related records for ObjectID: ", features[0].attributes.OBJECTID);
return;
}
fset = relatedRecords[features[0].attributes.OBJECTID];
for (var i=0 ; i < fset.features.length; i++) {
fset.features.attributes.LINK = "http://www.sc-pa.com/testsearch/parcel/" + fset.features.attributes.ID;
}
console.log(fset);
items = array.map(fset.features, function(feature) { //
return feature.attributes;
});
for (var i=0 ; i < items.length; i++) {
items.JUST = parseInt(items.JUST); //parses numeric integer (parseInt) and float (parseFloat) into an real number
}
for (var i=0 ; i < items.length; i++) {
items.ASSD = parseInt(items.ASSD);
}
for (var i=0 ; i < items.length; i++) {
items.LSQFT = parseInt(items.LSQFT);
}
//Create data object to be used in store
relData = {
identifier: "OBJECTID", //This field needs to have unique values
label: "OBJECTID", //Name field for display. Not pertinent to a grid but may be used elsewhere.
items: items
};
/* for (var i=0 ; i < items.length; i++) { //this items loop will get the IDs, but will only pass the last value to our hyperlink field
pid = items.ID;
console.log(pid);
}*/
//Create data store and bind to grid.
relStore = new Memory({
data: relData
});
//console.log(relStore);
relGrid.set("store", relStore);
//relGrid.set("query", {OBJECTID: "*"}); //filters what?
});
//if (!gridPane._showing) {
// gridPane.toggle();
//}
}
Not quite as elegant as yours but it works well and handles the links and sorting requierments needed for numeric columns in my dGrid. I was asking about moving to featureTable because I am looking for maybe a little better dom node solution because I want the dGrid to play well on tablets without maybe having to go to dojox.
Are you saying I should be able to pass this store into a featureTable instead of my dGrid?
