Latest Contributions by EdJuarbe

We are currently testing the Pipeline Tracking & Traceability data model and Arcade popup scripts developed by @TomDeWitte, and have stumbled on barcodes that do not conform to the ASTM F2897-15a 16 characters format. During our testing, we came across a valve whose barcode decoded to a value that exceeded the anticipated 16-character format. Before changing the field width, the OOTB arcade scripts were a simple drap/drop in our Attribute Expression dialog.  No other changes were made.  Simple changing the field Here's one example of the extracted barcode attribute: 'ELboG04njHV70Z90MW6 DEMO'.  To allow the capture of the extended characters, we attempted to create a new longer barcode field, but after doing so, the arcade scripts for the popup failed to save correctly, resulting in this error: 'Execution Error: Field not Found', which is odd since the field does exist, and prior to using a long field was not an issue.  I dug in and found by removing the '[text(C1FACTOR)] ' from the second to the last  line (Diameter & Wall Thickness scripts): 'var DIAM = DIAMETERDICTIONARY[text(C1FACTOR)];' the script allowed to save and the popup worked (although not sure what if what is being displayed is actually correct.  Similarly, the Diameter2 and WallThickness2 scripts has similar issue but removing the '[text(C2FACTOR)]' portion from the following line: var DIAM = DIAMETERDICTIONARY[text(C2FACTOR)]; allow the script to be saved.  The C1FACTOR was not a problem if the array was removed from the script entirely. So, I'm a little confused exactly what the C1Factor/C2Factor is actually doing, I'm faced with 2 options:  Modify the arcade script to get around the 'Field not Found' error. Find a way to automatically trim the barcode to 16 characters in the Field maps app.  We are currently manually removing the extra characters, which allows for the correct extraction of arcade popup values but which I feel is not going to be a reliable option.  Also, I would rather retain the full barcode value since it may contain additional information that would otherwise be lost if we don't retain it at time of installation. Would appreciate any help with this, or thought on better alternatives? TL/DR: Discovered barcodes longer than 16 characters.  Database fields wider than 16 characters cause the Diameter, Diameter2, Wall Thickness, & Wall Thickness2 arcade script to fail with 'Execution Error:Field not Found' when saving script. ... View more

Hi- We just completed an upgrade of our Portal Enterprise from 10.5.1 to 10.7.1 and have 2 issues that have yet to be resolved.  I do have each of these logged with ESRI, but while I wait for a response, would like to know if anyone experience these, or have any suggestions (aside from rebuilding out Web Maps and Apps) for me to try. 1. All of our popup definitions/configurations have gone missing for all Web Maps that were published prior to the upgrade.  This is seen when reviewing the popup dialog for each layer (in their respective web maps); the "Enable Pop-Ip",and "Configuration Pop-Up" options are not grayed out.  When you select these options, the base configuration dialog shows up (not the custom settings or definitions, that were set before the upgrade).  Also, when you click on the map, the pop-ups do not work.  While this is an issue, what's more puzzling is that the Web Application that use these web maps are showing the pop ups correctly.  My concern is if we update one layer's pop-up, it will save and remove all of the other popups in that web map.  Hoping someone has a graceful fix for this. Here's example of popup dialog for one layer of our published web map): Below is the unconfigured popup dialog: (web map that uses this popup does not display the popup (kind of expect that). However, below is a web application that consumes the above layer, and the resulting custom popup: Looking to find out where the application stored the pop-up definitions in case I need to replace them, if possible.  Better if there is a resolution to fix the pop ups in the web map. 2. When selecting a feature, the first feature shows the selection graphic correctly (overlaps the feature as expected), subsequent features selected shows a "random" selection graphic-feels like something is cached in the selection and displaying incorrectly.  Many of the selection graphics are close, but show additional vertices and in some cases are way different in geometry from the selected feature. Green line is the selected feature, cyan line is the selection graphic: Finally, this happened on our development server and p Thanks in advance! ... View more

Goal: I'm trying to create a collector (web map) so our users can collect a point for both the parent point feature, and the child point feature within a single Collector app (web map), while also being able to review the collected related tables from the attributes (pop-up label/View) panel.   Attempts: I've tried several approaches: Normal relationship class Reversing the relationship class, which allows me to have a single collection point for the inspections, but no way to also collect the parent feature point.  Adding 2 relationship classes (both the normal and the reverse relationship classes to the same tables, but opposite direction) thereby making both 'look' like parents (I was hoping).  While the geodatabase allowed me to create the relationship classes without so much as a blip, Collector would not display either layers in the 'Collect a new feature' panel. I finally tried to remove all relationship classes from geodatabase, and add them in ArcMap.  I received a warning that this produces an in-memory join, but was still able to publish the feature layer.  However, the relationship did not show in Collector. The only way to get both allowing to add points is to remove any relationship classes between both feature classes, which also removes any chance of validating the data from within the application. Is this simply not a viable workflow in Collector? It seems like Collector only displays the pop-up/attribute/relationship class view info for only one single parent feature class.  When presented with a double relationship to the same tables in the same feature service, Collector removes both from editing. I don't see why having both relationship classes should be reason to not allow both to be editable while allowing the display of the pop-up details, since the geodatabase allow this.  I think I'm slowly realizing the unfortunate answer, but thought I'd  ask those who may have found a way to get this to work, before walking away from this. My environment: I'm using ArcSDE 10.2.1, and ArcGIS Server 10.5.1 (on a federated Portal environment).   I'm currently using Collector 'Classic' v. 19.0.2. Finally, thanks in advance for any thoughts, recommendations, and suggestions. Ed J ... View more