Latest Contributions by williamcarr

Exact same issue. Did you ever have any luck? ... View more

Thanks Robert, this solved one of my issues as well. ... View more

Ian, Are you trying to create the domNode on the button click or just populate it? I use a button click to populate/remove content from an info widow using a domStyle toggle. To toggle Off: domStyle.set(query(".actionList > .action.sForm", window.map.infoWindow.domNode)[0], "display", "none"); To toggle On: domStyle.set(query(".actionList > .action.sForm", window.map.infoWindow.domNode)[0], "display", ""); Don't know if that helps any. ... View more

Is there a way to make a field active by default so that any field click would be the the second field ? ... View more

Do the graphics/points acquire a geometry after the zoom in/out event? I had some issue with this a year ago where a map click would query the x,y>create a graphic(invisible)>create a new feature in a feature layer>then applyEdits from the graphic geometry to the newly created feature. I noticed that the mouse location on a pan would update the graphic x,y before the apply edits took effect. Interesting how your points jump to the corner when the extent changes. Any updates on your progress? ... View more

I think you will have to load both feature services, regardless of whether or not you use a relate. It just depends which way you might want go-- relationship query or select a point and query with the selected point attribute. I'm actually updating my app to use the select and query option for an actual map rather than my previous map-less ui. I'll let you know when I hit paydirt. ... View more

This is exactly it. Mathew, are you sure you still need a relationship? It seems this queryTask might be easier to return your array. ... View more

Robert, I should be more specific. We are trying to have a feature on a map that the user can click on, after it is clicked the selected feature attribute is stored as a variable. This variable would then be used in a query to create an array of a Dojo chart(We got this part handled.) Popup | ArcGIS API for JavaScript For example, this popup example accesses attribute information, but the code doesn't show any click/selection code. I assume that there is a way to setFeatures, feature.attributes or access a feature index somehow. Not sure how. ... View more

Looks like I'm striking out. I'll post another thread in the JS forum and see if we can't Kelly and others to help us out. I'd really like to see a solution to this for personal reference. ... View more

I've never tried to access any sort of click event in an info window or popup yet so I'm unsure of how to pull a feature attribute, but I'll give it a shot tomorrow to see if I can't figure something out. ... View more

Yes, I created a relationship in my MapService, but I don't think you will need one. How did you initially planned to select the feature? ... View more

Ahhh. here is the whole function that I use to pull an attribute from a feature.(Sorry I don't have time to clean it up or test it or figure out the necessary portions. .) You could be able to extract that attribute, in this example 'hydrantRecord', and use it in your query. If i get some more time I'll try to come up with a better tested example if I get some time today.           map.on("click", function(evt) {               var selectionQuery = new esri.tasks.Query();         var tol = map.extent.getWidth()/map.width * 30;         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");                  });           });     var record = document.getElementById('record'); //add event listener record.addEventListener('click', function(e3) {   m5.on("click", lang.hitch(this, onLayerClick2));     var relatedTable2 = new FeatureLayer("http:", {         mode: FeatureLayer.MODE_ONDEMAND,         outFields: ["*"],         id: "relatedTable2"     });   console.log("Ran over the related table");           relatedTable.on("load", lang.hitch(this, function () {       console.log("RelatedTable Load");         var layerInfos = [         {                 'featureLayer': relatedTable2,                 'showAttachments': false,                 'isEditable': true,                 'fieldInfos': arrayUtils.map(relatedTable2.fields, function (field) {                 return {                     'fieldName': field.name,                         'isEditable': field.editable,                         'tooltip': field.type,                         'label': field.alias                 };             })         }                  ];                 var attInspector = new AttributeInspector({             layerInfos: layerInfos         }, domConstruct.create("div"));         attInspector.on("attribute-change", function (evt) {             evt.feature.attributes[evt.fieldName] = evt.fieldValue;             evt.feature.getLayer().applyEdits(null, [evt.feature], null);         });         attInspector.on("delete", function (evt) {             evt.feature.getLayer().applyEdits(null, null, [evt.feature]);             map.infoWindow.hide();         });         map.infoWindow.setContent(attInspector.domNode);         map.infoWindow.resize(350, 400);     }));       console.log("Record start")         function onLayerClick2(evt) {                 map.infoWindow.setTitle("Searching for related items...");             map.infoWindow.show(evt.screenPoint, map.getInfoWindowAnchor(evt.screenPoint));               //-------------------this is what is pulling the attribute for querying   //-------------------this is what is pulling the attribute for querying   hydrantRecord = evt.graphic.attributes.HydrantID; console.log(hydrantRecord);   //-------------------this is what is pulling the attribute for querying   //-------------------this is what is pulling the attribute for querying      //Done pulling the valve ID            var graphicAttributes = evt.graphic.attributes;             var title = graphicAttributes[m5.displayField];             var objectId = graphicAttributes[m5.objectIdField];             var relatedQuery = new RelationshipQuery();             relatedQuery.outFields = ["*"];             relatedQuery.relationshipId = 5;             relatedQuery.objectIds = [objectId]; console.log("relate found?"); console.log(relatedQuery.objectIds)             m5.queryRelatedFeatures(relatedQuery, lang.hitch(this, function (relatedRecords) {                 var fset = relatedRecords[objectId];                 if (fset) {                     map.infoWindow.setTitle(title || "No Title");                     var relatedObjectIds = arrayUtils.map(fset.features, function (feature) {                         return feature.attributes[relatedTable2.objectIdField];                     });                     var selectQuery = new Query();                     selectQuery.objectIds = relatedObjectIds;                     relatedTable2.selectFeatures(selectQuery, FeatureLayer.SELECTION_NEW); console.log(feature.attributes)                 } else {                     map.infoWindow.setTitle("No Related Items");                 }             }));             }     }); ... View more

Could you clarify on how the line and point are related? From my understanding, you have a line and a point with a common field, then select a line and display the point attribute with the line attribute based on a similar field? I have a few apps where I pull a single attribute from a feature I just selected. I use it to get water hydrant ID's when our service guys click on a hydrant. hydrantRecord = evt.graphic.attributes.HydrantID; This is how I pull the hydrant ID from a relationship query. Then I take this universal variable and plug it into my forms. It seems this would make your attribute data available for query later on. Are you planning on using the attribute inspector, infowindow....? ... View more