Latest Contributions by Billy

Hi, I'm looking for recommendations on the best workflow to update the source data (csv file) for my pulldata function in Survey123. Pulldata is used to lookup values from the csv file. I need to updated the csv file every other day. Regards. ... View more

Hi, I'm new to Survey123, so maybe this question is well known for long time users, but I couldn't find an explanation in GeoNet. In the UC 2020 there was a session titled "Survey123: What's New", during the presentation (@8:43) the new folders options are discussed and the "Inbox" folder is shown with some surveys, then presenter clicks the refresh button in the inbox and says that this is doing a query to the server that returns a new survey that has been assigned to me.  How to make this assignment of surveys to specific field workers is the reason of my question. Is this done in combination with Workforce or in the feature layer in AGOL or another way? Is there any documentation about the workflow to do this? ... View more

Hi, Before the recent update of Survey123, I tested successfully reading the barcode of our electric meters nameplate  using the Barcodes sample survey available in Survey123 Connect (version 3.9) and the android mobile app. This is the barcode that I'm trying to scan: After upgrading to Survey123 Connect v3.10, I created a form hoping to use the barcode reading functionally of the app but now the barcode question doesn't detect the barcode. I also tried with the Barcodes sample survey again to no avail. I read this blog post, from May-2016, about the Barcode Question: https://community.esri.com/groups/survey123/blog/2016/05/17/understanding-barcode-questions-in-survey123-for-arcgisThe post list the barcodes recognized by the app: Survey123 for ArcGIS supports a very specific subset of them: QR Code, Code 39, Code 93, Code 128, EAN 8, EAN 13, UPC A, UPC E, UPC EAN Extension, Aztec, Codabar, Data Matrix, ITF, MaxiCode, PDF 417, RSS14 and RSS Expanded.  Also, the article mentions that: If scanning fails, the first thing to check is if Survey123 is configured to scan the type of barcode you are targeting.  Use the menu button in the top-right corner to configure the scanner.   You can configure the barcode scanner to scan any of the supported types if you like. I selected all the options available in the menu option with no change in the result. I was surprised that I could not select all the types at the same time, as I tried to select them one by one some of the previously selected lost their selection. Also, the list of barcode type available after the upgrade is the same the was available before. So, it doesn't look like the barcode type I'm trying to scan was removed from the list. In addition, I had another problem with the rotate camera button. After clicking it once the camera rotated to the front facing camera and it won't change to the back camera when clicking it again or closing and opening the app. How I can solve these problems. Thanks. ... View more

Hi, Is it possible to change the font size and/or type of a form in Survey123 Connect? I know that the font size of labels can be changed with HTML, but what I'm looking for is a way to change the font size and/or type for the whole form. This mean changing the font inside the input boxes, notes, selection question options, etc. ... View more

Hi, Here are details of the different utility network environments I have set up:   * Electric Asset Package 3.4, deployed in SQL Server 2017 with sample data. The ArcGis Enterprise was 10.8, ArcGis Pro 2.5.2 and utility network version 3. I WILL CALL THIS SAMPLE ENVIRONMENT.  * Electric Asset Package 3.3, deployed in SQL Server 2017 as schema-only and spatial reference changed to our location. The ArcGis Enterprise was 10.8, ArcGis Pro 2.5.2 and utility network version 3. After the deployment additional configuration was done to the UN, like: adding field, domains, asset_types and 2 editing versions. I WILL CALL THIS THE DEVELOPMENT ENVIRONMENT.  * Electric Asset Package 3.4, deployed in SQL Server 2017 as schema-only and spatial reference changed to our location. The ArcGis Enterprise was 10.8, ArcGis Pro 2.5.2 and utility network version 3. After the deployment additional configuration was done to the UN, like: adding field, domains, asset_types and 1 editing versions. I WILL CALL THIS THE PRODUCTION ENVIRONMENT. When Pro 2.6 was pushed at the end of July, I updated my Pro client. Then with the Pro 2.6 client, I exported the Asset Package of the PRODUCTION ENVIRONMENT and deployed in a File Geodatabase (FGDB). When I check the Utility Network Properties the Utility Network version is 4. I WILL CALL THIS THE TEST ENVIRONMENT. NOW THIS IS THE PROBLEM: I created and successfully tested an Arcade rule in the TEST ENVIRONMENT. The rule is assigned to the StructureJunction/Electric Medium Voltage Pole. The rule returns a dictionary that updates some fields of the Electric Medium Voltage Pole feature, adds records to the related table JointUse and adds one or more feature to the ElectricDevice/Low Voltage Light. The pictures show the attribute rule window and the dictionary returned bye the rule. Then I tried to the rule in the PRODUCTION ENVIRONMENT after changing the classNames with EGDB reference name. The rule failed with this error message: The rule was also tested in the DEVELOPMENT ENVIRONMENT with the same result, but the error message was a little different, this is from the ArcGis Server Manager Log: I tried returning only part of the dictionary and I found that the rule only failed when the returned dictionary has the section that adds the Street Light and Flood Light to the ElectricDevice class, as you can see above in the picture with the returned dictionary. After identifying that the error is trigger when adding to the ElectricDevice class, I decided to test a simpler rule in the 3 EGDB environments (SAMPLE, DEVELOPMENT and PRODUCTION). The simpler rule failed, with the same error message as shown above, in all but the SAMPLE ENVIRONMENT. Here is the code of the tested rule, in every case the claseName was changed to match the database: //low voltage pole geometry var featureGeo = Geometry($feature) //create the geometry for the street light var slGeo1 = Point({'x': featureGeo.x + 8, 'y': featureGeo.y + 8, 'z': 0, 'spatialReference': featureGeo.spatialReference}) return { 'result': 'processed', 'edit':[{ 'className': 'UN_PMLP_V34.UNPMLPV34.ElectricDevice', 'adds':[{ 'attributes': { 'AssetGroup': 16, 'AssetType': 302, }, 'geometry': slGeo1, 'associationType': 'attached' }] }] } After calling Esri's Tech Support, I received the recommendation to upgrade all the clients to the correct version to comply with the requirement of this link: Utility network dataset administration—ArcGIS Pro | Documentation and this table: After 2 days of upgrades and calls to tech support, ArcGis Enterprise was upgraded to 10.8.1, the geodatabases for the DEVELOPMENT and PRODUCTION ENVIRONMENT were upgraded, as well as the corresponding Utility Network Datasets, to version 4, in both environments. Additionally the utility networks in both environment were publish under new names, because the original services couldn't be re-started after they were stop to upgrade the Utility Network Dataset. At the end of all this, the rule error persist in both environment (DEVELOPMENT and PRODUCTION) and the rule works in the SAMPLE ENVIRONMENT, even when the Utility Network Dataset was not updated to version 4. The log of the Arcgis Server Manager has this report. It makes a reference to line 11 of the Script, but the is no code on line 11 of the Script. Esri's Tech Support has a copy of the exported Asset Package and SQL Database of the PRODUCTION ENVIRONMENT. ... View more

Hi, Is it possible to create cascading select in Survey123 with overlapping option? The image shows choices. As the image shows there are multiple options that have overlapping options when filtered. This is the code that I add to the "choice_filter" column: single_polemount=${transformer_type} or three_polemount=${transformer_type} or single_padmount=${transformer_type} or three_padmount=${transformer_type} ... View more