Latest Contributions by MKF62

I create a definition expression on a featureLayer through it's relationship with table. The definition expression gets applied to the table first, then the definition expression for the featureLayer is created and applied. The definition expression is pulling records of a certain year in the table, then through it's relationship with the featureLayer I get GUIDs of those that match the pulled records in the table and set the featureLayer's definition expression based on those GUIDs. The problem is that for some years this works and for others it doesn't. I can see in the debugger that the definition expression gets created correctly for the featureLayer, but when I apply it to the featureLayer, nothing displays on the map. If I switch the year to another year, the definition expression gets applied and the appropriate polygons appear for that year. If I switch back to the previous year, again, no polygons are displayed, even though they exist for that year. It's pretty odd behavior and I'm not sure why this would be happening. Records in the table when the definition expression is set to YearTreated = 2015. Records in the related feature layer that match these MgmtTractIDs My code should produce a definition expression like this for application to the featureLayer: var de = "MgmtTractID = '{...}' OR MgmtTractID = '{...}' OR MgmtTractID = '{...}'‍ ..so on and so forth Apply that definition expression to the feature layer and I get nothing displayed on the map. This definition expression works for 2009, 2010, 2011, 2012, 2013, 2014, 2017, 2018, and 2019. It doesn't work for 2008, 2015, or 2016. I have checked and rechecked that the DE is being created correctly with formatting and that the MgmtTractIDs do indeed show up in the related feature layer. Everything looks fine.  on(dom.byId("data-year"), "change", function () { var year = dom.byId("data-year").value; //Defintion expressions are already set upon first load of the map, don't need to recalculate //if the year hasn't been changed. A change event is fired on load of the map. if (year !== currentYear) { hbMgmtTableFL.setDefinitionExpression('YearTreated = ' + year); hbMgmtTableFL.refresh(); //The habitat management feature layer needs to be filtered using the related table. getTractDefExpression(); } }); function getTractDefExpression() { var recordIDs = new Query(); recordIDs.where = "1=1"; hbMgmtTableFL.queryIds(query, function (OIDs) { if (OIDs !== null) { //Create relationship query var relatedRecordsQuery = new RelationshipQuery(); relatedRecordsQuery.objectIds = OIDs; relatedRecordsQuery.outFields = ["MgmtTractID"]; relatedRecordsQuery.relationshipId = 0; hbMgmtTableFL.queryRelatedFeatures(relatedRecordsQuery, function (fset) { //Get all MgmtTractIDs for the current year from the table //The table already has it's definition expression set, so it'll //only pull the MgmtTractIDs for the year that is set var MgmtTractIDsArr = []; for (i = 0; i < OIDs.length; i++) { var OID = OIDs[i]; var features = fset[OID].features; var mgmtTractId = features[0].attributes.MgmtTractID; if (!(MgmtTractIDsArr.includes(mgmtTractId))) { MgmtTractIDsArr.push(mgmtTractId); }; } //Create the definition expression for the feature layer var whereClause; for (i = 0; i < MgmtTractIDsArr.length; i++) { if (i == 0) { whereClause = "MgmtTractID = '" + MgmtTractIDsArr[i] + "'"; } else { whereClause = whereClause + " OR MgmtTractID = '" + MgmtTractIDsArr[i] + "'"; } } //Set the polygon feature layer's definition expression based on the GUIDs debugger; hbMgmtTractFL.setDefinitionExpression(whereClause); hbMgmtTractFL.refresh(); }); } else { debugger; hbMgmtTractFL.setDefinitionExpression('MgmtTractID = 0'); hbMgmtTractFL.refresh(); } }); };‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍ ... View more

I have a InfoTemplate that sets content based on the click of a feature. When people switch through features using the arrows on the popup, the function that sets the content does not fire. I imagine the arrows do not count as a click event, how do I handle this? There are three features that overlap each other, two of them are in the same feature class, one of them is a different feature class. Switching with the arrows between the two feature classes show the appropriate popups for each, but the feature layer with the two features selected uses the same information in both popups as the content is set based on a click. If I click either of these features independently where they do not overlap, their content sets correctly. hbMgmtTractFL.on("click", function (feature) { var OID = feature.graphic.attributes.OBJECTID; relatedTractAttrb('popupContent', OID); }); function relatedTractAttrb(purpose, oids) { //set all the content }‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍ I have looked at the documentation and I don't see a clear event for switching between features with the arrows. I thought it was supposed to act as a click event, but I suppose not? ... View more