Latest Contributions by JayHodny

Laura, Many thanks!  I usually forget about that one important detail. Regards, Jay ... View more

I think I have this figured out.  In this example, I have a starting inventory of 188 95 gallon recycle carts. I pulled seven carts from inventory and the result is 181 remaining.  The Indicator element is filtering the cart type, cart size and cart transaction where carts are pulled from inventory and delivered to residents. var difference = 188 - $datapoint["count"] return { middleText: difference } ... View more

Ah make sense Daniel, many thanks. ... View more

I was comparing the 'Trees' feature service with 'Trees_public' service after I deployed the solution.  If I am not mistaken, the _public service does not have a field called "adoptedby."  Just curious as to why. ... View more

Perfect Daniel, thanks! ... View more

Hi Barry, Thanks for the reply.  The "map frame" phrase was a poor choice to use.  I failed to mention that definition queries were involved as well, with multiple maps each with different queries filtering the same data.  I was looking for a lazy way to keep things straight and organized.  Regards, Jay ... View more

Bingo!  I think I have this resolved.  I modified the script to remove the 'L0ServiceLine' in the field name, and this restored the dots in my wLSL feature class.  I don't know how this happened in the first place, but I know what to do going forward.  Thank you again for your help. ... View more

Hi Alex, I believe the dot labeling issue has to do with the join I have in place.  It appears the Arcade labeling code from the original solution gets updated or overwritten based on the newer field names.  In testing in a separate Pro project, if I replace the Arcade code with the code from the original solution the dot labeling returns. Original Solution Arcade code if($feature.utilverified != "Yes" && $feature.custverified != "Yes") {return " ●●"} else if($feature.utilverified != "Yes" && $feature.custverified == "Yes") {return "●"} else if($feature.custverified != "Yes" && $feature.utilverified == "Yes") {return " ●"} My feature class Arcade code. I have no clue why the Survey123 L0ServiceLine field names are shown or where this comes from?  wLSLServiceLines is my feature class on sde, created from the ServiceLine layer, and represents our source of truth.  Again, the dot labeling and symbology were working fine for the past several months with this feature class.  I think I can simply replace the current code with the solution's original code and all will be well.  I would like confirmation though.  And thank you for your help! if($feature['.....wLSLServiceLines.L0ServiceLine.utilverified'] != "Yes" && $feature['.....wLSLServiceLines.L0ServiceLine.custverified'] != "Yes") {return " ●●"} else if($feature['.....wLSLServiceLines.L0ServiceLine.utilverified'] != "Yes" && $feature['.....wLSLServiceLines.L0ServiceLine.custverified'] == "Yes") {return "●"} else if($feature['.....GIS.wLSLServiceLines.L0ServiceLine.custverified'] != "Yes" && $feature['.....wLSLServiceLines.L0ServiceLine.utilverified'] == "Yes") {return " ●"}   ... View more

Hi Alex, Yes, I have been updating the verified fields.  The dots have been present for months, disappearing as expected, when I update the verified fields.  The Arcade code is present in the labeling properies pane.  On top of this, I began to have trouble Friday with symbology failing during a join to another layer.  Maybe the two, labeling and symbology, are related?  In addition, to updating my LSL FC with the Survey123 results, I was attempting to bring over water main, curb stop, and lateral line material values from the other sde FCs, to better populate the service line layer.  I started getting the following error message:  Warning: Primary symbology relies on one or more fields that are invalid. I found a technical bulletin work around which helped me correct the symbology issue, but the dot labelling was never restored.  I really don't know what else to do.  I have updated10,000 records and worry about something being corrupted.  I was close to concluding the historic data search, and now the above starts to happen. ... View more