Latest Contributions by LeaHarper

‎08-19-2020

Hey Xander Bakker - Just did a quick IIF statement to verify the globalIDs and all came back correctly. It almost seems like the issue is specifically on the Filter function - even when I try simplifying the sql variable or hard coding the filter function to something specific like below, the parse error is still thrown. var related_data = Filter ( tbl , tbl [ "cap_iss" ] == "test" ) ; ‍ ‍ Is it possible there is some kind off setting I may have missed with the feature service was published to Portal? I've verified that it supports both standardized and advanced queries. I don't know if it makes a difference, but here is the webmap we're fiddling in. And thank you - I do really appreciate your help even though this is giving us a good go-around.

‎08-19-2020

Thanks for getting back to me so quickly, Xander Bakker‌! I swapped out the sql variable for what you suggested, but I am still getting that error " Execution Error: Cannot read property 'parse' of undefined" when I try returning related_data. I'm not really sure what to make of this since I can't get a more detailed error message... Also, I see what you mean about the max date and made that correction in my draft (thank you!)... I will very much look forward to having the " FeatureSetByRelationshipName" function available when we upgrade to 10.8.

‎08-19-2020

Hi Xander Bakker‌! I've been trying to achieve the very similar results as the others above, but keep getting hit with the error " Execution Error: Cannot read property 'parse' of undefined" that seems to occur at the Filter function. Here is the first part of the code that I have created: //Read out the GlobalID of the seawall feature layer var id = $feature [ "globalid" ] ; //Create a sql expression to query on GlobalID var sql = "wall_id = '" + Upper ( id ) + "'" ; //Get related table var tbl = FeatureSetByName ( $datastore , "Seawall Inspections" ) ; //Filter the table using the sql expression var related_data = Filter ( tbl , sql ) ; //check filter return related_data‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ Once I check to see if the filter works, that's when the parsing error comes back... I also tried changing the sql variable but that didn't change the error. //Create a sql expression to query on GlobalID var sql = "wall_id =" + id + "" ; ‍‍‍‍ ‍ ‍ The data that I'm using is a Portal-hosted feature service containing a seawall feature layer and related inspection table. The relationship is 1:Many and the globalid field of the feature layer and wall_id field of the related table tie them together. At the end of the day, what I'm trying to do is pull the most recent inspection record date from the related table into the popup for the feature layer. This is what I imagine the final script will look like: //Read out the GlobalID of the seawall feature layer var id = $feature [ "globalid" ] ; //Create a sql expression to query on GlobalID var sql = "wall_id = '" + Upper ( id ) + "'" ; //Get related table var tbl = FeatureSetByName ( $datastore , "Seawall Inspections" ) ; //Filter the table using the sql expression var related_data = Filter ( tbl , sql ) ; ‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍ //Count the resulting records var cnt = Count ( related_data ) ; //Initiate a variable to hold the result var result = "No inspections available." ; //Check if there are related records found for the current GlobalID if ( cnt > 0 ) { result = "Inspections: " + cnt ; //Get most recent inspection var max_date = Top ( OrderBy ( related_data , 'insp_date DESC' ) , 1 ) ; for ( var related_data in related_data ) { result + = TextFormatting . NewLine + "Most recent inspection: " + max_date ; } } return result ; ‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ If you could help me figure out what I am missing, I would be so grateful!

‎07-07-2020

Found another post discussing the same issue and referencing a bug in Portal: https://community.esri.com/thread/247938-duplicate-objectidsfeatures-in-view-layer

‎05-22-2020

Hello! My colleague Ian McNair‌ and I have been around the ringer trying to figure out an issue with a survey we created on a related table. As far as we can tell, the survey was created successfully - meaning new submissions appear in the related table and as long as the GlobalID from the point feature is pulled in using URL parameters, the related records are associated with the point feature. That being said, any time a submission is made to the survey, a new "ghost" point feature is also created. This feature has no geometry and the only attribution is what pulls in through the URL parameters. What's also odd is this feature also has no relation to any records in the related table. The workflow we used for creating the survey is as follows: Creating the Survey Using Survey123 Connect, created survey from an existing feature service hosted in our organization's Portal (not ArcGIS Online). Removed all fields related to the point feature and the repeats, leaving behind only the fields of the related table. Under the Settings tab of the excel sheet, updated the form_id to match the name of the related table as it appears in the service URL. Tying into a Web App In a web application (Web AppBuilder), I created a custom popup on the point feature to include the Survey123 web form link. The survey link also pulls in the following URL parameters from the point feature: Company - as a read-only field for the user's reference - into the related table's "company" field GlobalID - to maintain the relationship between the point feature and the record in the related table - into the related table's "ibp_u_id" field ----------------------------------------------------------------------------------------- Once we have the survey set up for submission, we can't understand why we're getting the behaviors below: Scenario 1: Everything configured exactly as described above The survey successfully pulls in the point feature's Company and GlobalID fields. Upon submitting the survey: The submission appears in the related table When clicking on the point feature, we can see the submission as a related record The submission generates a new feature in the point feature service. This "point" does not have geometry and contains the Company and GlobalID field pulled in from the URL parameters - all other fields are blank. Scenario 2: Remove the Company field from the URL parameters The survey successfully pulls in the point feature's GlobalID field Upon submitting the survey: The submission appears in the related table When clicking on the point feature, we can see the submission as a related record The submission generates a new feature in the point feature service. This "point" does not have geometry and contains GlobalID field pulled in from the URL parameters - all other fields are blank. Scenario 3: Remove the Company and GlobalID fields from the URL parameters Upon submitting the survey: The submission appears in the related table but is not related to any point feature The submission generates a new feature in the point feature service. This "point" does not have geometry and all other fields are blank. ----------------------------------------------------------------------------------------- We're not sure where to go from here or how to identify where the hangup is. We've also tried republishing new services in the case something became corrupted behind the scenes but in the end we're still getting the "ghost point" that shouldn't be there. Any help is greatly appreciated - we're ready to get this working so we can roll it out! James Tedrick‌? Ismael Chivite‌? Resources: Survey123 Web Form (XLSX file attached) Web Map Web Application Published Feature Service - Portal Item Thank you! - Lea Harper

‎12-20-2019

Thanks Brandon! That fixed everything and the survey works flawlessly now in both the web form and app.

‎12-17-2019

Hello! I created a survey in Survey123 Connect and one of the calculations uses the concat and pulldata functions to pre-populate the geopoint question from a CSV file in the media folder. In both connect and the Survey123 app, the results work flawlessly. However, we plan to use this survey through the web form and whenever I try to load it, I receive the following error: FormLogicError: instance 'property' (the CSV file) does not exist in model I'm not entirely sure where the error is since we duplicated this method from a working Survey123 item. For that one, both the web form and the Survey123 app work without a hitch. I've attached the files for the survey in question if anyone has suggestions for what I may be missing? If its relevant, this survey is hosted through our organization's ArcGIS Portal and all content is shared publicly. Link to Web Survey

‎07-16-2019

I've had a couple challenges in the past with an ArcGIS Pro map series not exporting all the pieces on a page, where I would just go back and export that single page after. This is a new one, though. For whatever reason, exporting this map series into individual pages has ended with the majority of text characters looking like they are not supported? The font for the entire document is set up 10pt. Arial in uppercase, with some bold or underlining here and there, but I can't figure out why some pages export the content correctly and others don't. When I export the series in a single PDF, the content is perfect. There are a decent number of pages in the single PDF that all need to be separated out and renamed, so I'm hoping there's some way to fix this, or perhaps a best practice for fonts that I don't know about that Pro is known to have issues with? Thanks for the help!

‎03-29-2019

Hi Dan - I've defined the primary key as parcel_id (which does have duplicate values in the original dataset), but I made sure to call distinct values in the query. Could Pro somehow be picking up on duplicates in the background when the query runs?

‎03-29-2019

I created a query layer in ArcGIS Pro from a feature hosted in our SDE that looks like so: select distinct parcel_id , primary_address , owner , shape from parcel . parcels_master_mv where ( UPPER ( owner ) LIKE 'MANATEE COUNTY%' OR owner LIKE 'MANATEE, COUNTY%' OR owner LIKE 'COUNTY OF MANATEE%' OR owner LIKE '%CEMETERY%' OR owner LIKE '%CEMATERY%' OR owner LIKE 'SIXA INV%' OR owner LIKE 'TIITF%' ) AND ( LUC IN ( '7600' , '8086' , '8600' , '9400' , '9500' ) ) AND ( UPPER ( owner ) NOT LIKE '%MOSQUITO%' AND UPPER ( owner ) NOT LIKE '%PORT%' AND UPPER ( owner ) NOT LIKE '%AUTHORITY%' AND UPPER ( owner ) NOT LIKE '%HOUSING%' AND UPPER ( owner ) NOT LIKE '%HABITAT%' AND UPPER ( owner ) NOT LIKE '%AUDOBON%' AND UPPER ( owner ) NOT LIKE '%BANK%' AND UPPER ( owner ) NOT LIKE '%CHURCH%' AND UPPER ( owner ) NOT LIKE '%FAMILY%' AND UPPER ( owner ) NOT LIKE '%FARM%' ) order by parcel_id desc ‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ Why I believe there's a bug is because when I open the attribute table and start scrolling, I get an error a couple rows in that says "Failed to retrieve a page of rows." After I select okay, the attribute table crashes - and it does so at the same point every time I reopen the table. When I remove the "order by" command, I can scroll freely though the attribute table without error. It seems to be very similar to this bug that was reported resolved with Pro 2.3: What does "Failed to retrieve a page of rows" imply?‌

Online Status	Offline
Date Last Visited	‎11-11-2020 02:23 AM

My Ideas

Latest Contributions by LeaHarper

Re: How do you reference another field from a related table in Arcade?

Re: How do you reference another field from a related table in Arcade?

Re: How do you reference another field from a related table in Arcade?

Re: Survey123 Publishing to Related Table Successfully, But Creating New Records in Related Feature Service?

Survey123 Publishing to Related Table Successfully, But Creating New Records in Related Feature Service?

Re: Survey123 web form not recognizing pulldata CSV?

Survey123 web form not recognizing pulldata CSV?

Map Series Not Supporting Text Characters in Export?

Re: Possible Bug with Query Layer Attribute Table in Pro?

Possible Bug with Query Layer Attribute Table in Pro?