topic Re: Related table in Attribute Inspector in ArcGIS JavaScript Maps SDK Questions

Related table in Attribute Inspector

williamcarr — Wed, 13 Aug 2014 19:21:37 GMT

Greetings,

I am having considerable trouble getting the results from a relationship query to populate an attribute inspector(for editing purposes). I have been working on this for a few weeks now and am having no luck.

Takes two clicks before the related info will pop up in a infowindow.

 function findRelatedRecords(features) {
        var relatedTopsQuery = new esri.tasks.RelationshipQuery();
        relatedTopsQuery.outFields = ["*"];
        //relatedTopsQuery.relationshipId = 3;
        relatedTopsQuery.relationshipId = 0;
        //relatedTopsQuery.objectIds = [features[0].attributes.OBJECTID];
        relatedTopsQuery.objectIds = [features[0].attributes.OBJECTID];
        wellFeatureLayer.queryRelatedFeatures(relatedTopsQuery, function(relatedRecords) {
          console.log("related recs: ", relatedRecords);
          if ( ! relatedRecords.hasOwnProperty(features[0].attributes.OBJECTID) ) {
            console.log("No related records for ObjectID_1: ", features[0].attributes.OBJECTID_1);
            return;
          }
          var fset = relatedRecords[features[0].attributes.OBJECTID];
          //var fset = relatedRecords[features[0].attributes.OBJECTID];
          items = dojo.map(fset.features, function(feature) {
            return feature.attributes;
          });
          
       

      function findWells(evt) {
  var asdf = evt.layers[0].layer;
          var selectQuery = new Query();
        var selectionQuery = new esri.tasks.Query();
        var tol = map.extent.getWidth()/map.width * 5;
        var x = evt.mapPoint.x;
        var y = evt.mapPoint.y;
        var queryExtent = new esri.geometry.Extent(x-tol,y-tol,x+tol,y+tol,evt.mapPoint.spatialReference);
        selectionQuery.geometry = queryExtent;
        
             asdf.selectFeatures(selectionQuery, FeatureLayer.SELECTION_NEW, function(features) {
             
               //store the current feature
                updateFeature = features[0]; console.log("adf");
                map.infoWindow.setTitle(features[0].getLayer().name); console.log("adf");
                map.infoWindow.show(evt.screenPoint,map.getInfoWindowAnchor(evt.screenPoint)); console.log("adf");
     
            });
            
            
          };
// I am also unable to get the attribute inspector to pull up a non related feature  BELOW
    var layerInfos = [{
            'featureLayer': wellFeatureLayer1,
            'showAttachments': false,
            'isEditable': true,
            'fieldInfos': [
              {'fieldName': 'SERVICE_ID', 'isEditable':true, 'tooltip': 'Current Status', 'label':'Status:'}
            ]
          }];


          var attInspector = new AttributeInspector({
            layerInfos:layerInfos
          }, domConstruct.create("div"));

Any help would be very much appreciated.

Re: Related table in Attribute Inspector

KyleBelott — Wed, 13 Aug 2014 22:16:12 GMT

Hi William,

I had attempted this almost 2 years ago (v 2.7) with no success using RelationshipQuery. After several discussions with Support, I was told it couldn't be done and would be logged as NIM081851.

Here's what ended up working for me.

https://community.esri.com/message/253305#253305

I hope it helps you out.

Kyle

Re: Related table in Attribute Inspector

JohnGrayson — Wed, 13 Aug 2014 23:14:44 GMT

Will, the workflow would be something like this:

Create FeatureLayer for related table
Create AttributeInspector using FeatureLayer from previous step
For any source feature, find related features and create list of ObjectIds
Select related features in the related FeatureLayer based on related ObjectIds

Edit Related Features - JSFiddle‌

Re: Related table in Attribute Inspector

williamcarr — Thu, 14 Aug 2014 12:40:24 GMT

Appreciate the help guys!

Kyle, I actually found your work around after I posted this yesterday. I understand the logic but I'm drawing a blank on how the query should go. I'd really like to see this work for a better understanding of query abilities.

query2 = new esri.tasks.Query();
query2.where = "serviceID = '" + selectedFeatures?? + "'";
query2.outFields = ["*"];
activityRecord.selectFeatures(query2, esri.layers.FeatureLayer.SELECTION_NEW);

Re: Related table in Attribute Inspector

williamcarr — Thu, 14 Aug 2014 12:48:33 GMT

John, that fiddle worked out pretty good. I've never used lang.hitch, so I guess I have some documentation to go through.

Thanks again.

Re: Related table in Attribute Inspector

KyleBelott — Thu, 14 Aug 2014 13:18:30 GMT

Unfortunately, I don't have a live website to show anymore and the original feature services have been relieved of duty. Essentially, query2 is querying the attribute of the selected feature in the "related" table (activityRecord in my case). You may have success with something like:

query2.where = "serviceID = '" + selectedFeatures[0].attributes.serviceID + "'";

So long as you have the serviceID attribute present in both the feature layer and table it should come back with results. Then identify the "featureLayer" property as "activityRecord' for the "layerInfos" object, and specify "layerInfos" in "attInspector" for the "layerInfos" property. I believe it should then hydrate the Inspector with the query2 results.

If I get some time this weekend maybe I'll spin up some services for an example.

In the mean time, let me know if there's more clarity I can provide.

Kyle

Re: Related table in Attribute Inspector

JohnGrayson — Thu, 14 Aug 2014 15:31:55 GMT

Will, I like to use "lang.hitch(...)" to provide proper context (what 'this' means) to any function that runs async Since a lot of the JS API methods return Deferred, this becomes a simple and powerful coding pattern.

Re: Related table in Attribute Inspector

williamcarr — Thu, 14 Aug 2014 16:49:29 GMT

Kyle, here is what I got going as of nowbut it still won't populate the field.

function initSelectToolbar(evt) {
          var asdf = evt.layers[0].layer;
          var selectQuery = new Query();


          map.on("click", function(evt) {
              var selectionQuery = new esri.tasks.Query();
        var tol = map.extent.getWidth()/map.width * 15;
        var x = evt.mapPoint.x;
        var y = evt.mapPoint.y;
        var queryExtent = new esri.geometry.Extent(x-tol,y-tol,x+tol,y+tol,evt.mapPoint.spatialReference);
        selectionQuery.geometry = queryExtent;
            
            
      
            asdf.selectFeatures(selectionQuery, FeatureLayer.SELECTION_NEW, function(features) {
             
               //store the current feature
                updateFeature = features[0]; console.log("adf");
                map.infoWindow.setTitle(features[0].getLayer().name); console.log("adf");
                map.infoWindow.show(evt.screenPoint,map.getInfoWindowAnchor(evt.screenPoint)); console.log("adf");
     
           activityRecord = new esri.layers.FeatureLayer("/Relate1/FeatureServer/1", {  
  infoTemplate: recordTemplate,  
  outFields: ["*"],  
  id: "activityRecord"  
});  
console.log("asdf1");


       query2 = new esri.tasks.Query("Relate1/FeatureServer/1");  
       
       //  related table field          point feature selected field
query2.where = "serv_id = '" + selectedFeatures[0].attributes.Service_ID + "'";
query2.outFields = ["*"];  
activityRecord.selectFeatures(query2, esri.layers.FeatureLayer.SELECTION_NEW);  
       
console.log("asdf2");
       
       layerInfoss = [{ 'featureLayer': activityRecord,  
  'showAttachments': true,  
  'isEditable': true
}];  
  console.log("asdf3");
attInspector = new esri.dijit.AttributeInspector(  
  { layerInfos: layerInfoss   
     }, domConstruct.create("div1"));
  
  console.log("asdf4");
recordTemplate = new esri.dijit.PopupTemplate({  
  title: "{PROPERTY_ID}",  
  fieldInfos: [  
    { fieldName: "serv_id", visible: true, label: "Record:" }  
  ],showAttachments: true  
});

I have tried all sorts of combinations, so I'm not sure where exactly i'm screwing this up.

Re: Related table in Attribute Inspector

KyleBelott — Thu, 14 Aug 2014 17:26:02 GMT

I don't see any fieldInfos set in your layerInfoss object, but all fields should be returned anyways. This table is editable, correct? It may be an issue with the recordTemplate - title property being {PROPERTY_ID}. Do you have that field in your table? If not, change it to a field name from your table. You may want to try moving line 36 "activityRecord.selectFeatures(..." under the AttributeInspector constructor at line 48.

I use Chrome for console logging. Set some objects in console.log and look to see if they are holding the expected values.

Welcome to the "combinations" club!

Kyle

Re: Related table in Attribute Inspector

williamcarr — Fri, 15 Aug 2014 15:19:51 GMT

John,

I've got a pretty good understanding of your sample, but I'm running into some issues with applying it to my app. The issue is getting it to work with an existing attribute inspector with no related tables. I've tried adding the layerInfos in to the relatedTable.on("load", lang.hitch(this, function () ... No avail. I've tried using separate attribute inspectors.. no luck. each would work pending there was a map.infoWindow.setContent(attInspector1.domNode);, but not together. Any advice? I have a fiddle here Edit fiddle - JSFiddle‌ set up to use two attribute inspectors, and it also has the combined layerInfo as well. Would you mind taking a look to see where I'm dropping the ball.

Re: Related table in Attribute Inspector

JohnGrayson — Fri, 15 Aug 2014 17:03:47 GMT

Will, I don't understand the code in your jsfiddle, and there are many issues in there. It seems like you added a bunch of code that just tries to do similar things to what I was already doing, but then you also left my code in there. It doesn't make sense. Additionally, the sample map service you're trying to use doesn't have a FeatureService behind it, so I don't think its a good service to test this scenario out. Having a jsfiddle built against the real FeatureServices you are working with would really help.

- Don't create multiple instances of AttributeInspector, just add all your editable layers to one instance via layerInfos.

- Don't let the 'related table' concept confuse you, it's just another FeatureLayer that the AttributeInspecor can edit.

- Every layer added to the layerInfos of the AttributeInspector should have a list of fields you want to view/edit.

- If defining the editable fields dynamically from the FeatureLayer, then make sure the layer is 'loaded' before accessing the 'fields' collection.

I hope this helps

Re: Related table in Attribute Inspector

williamcarr — Fri, 15 Aug 2014 19:32:00 GMT

Ok, yeah that was pretty bad. Not sure what went on there, but I assure you I haven't been drinking.

I've loaded the layers in like in your samples, but the non related layer is still not popping up. I fixed the Fiddle Edit fiddle - JSFiddle , and it is returning the related table info but not the non related feature.(I realize that is just a Map Service, but it should still return a value. right?)

I think this is due to the all the selections running through the onSourceLayerClick(evt), not finding a value and turning up "No Related Items".

I appreciate all your help, John, do you think you could take one more look at it???

Re: Related table in Attribute Inspector

JohnGrayson — Fri, 15 Aug 2014 20:55:40 GMT

Will, there are several considerations to look at for this use case. The relationship query is specific to a layer, so the 'click' event should be on that layer, not the map. This routine only selects items from the related table, so those are the only ones that show up in the AttributeInspector. If you wish to see features from a different layer in the AttributeInspector you'll have to create a different 'selection' routine that is specific to that layer. You could have a generic 'selection' routine, but then you'd have to put logic in it to deal with each layer in a specific way.

Edit fiddle - JSFiddle‌

Re: Related table in Attribute Inspector

williamcarr — Sat, 16 Aug 2014 17:08:16 GMT

Good stuff, John. You got me out of a hell of a pickle. Appreciate all the help.