Latest Contributions by JosephMootz1

Hi Phil, Thanks for your answer. If I were to enter an enhancement request, I think the proper solution is for the developers to put the message in a status bar not a popup that requires user interaction. We have people entering hundreds of forms a day opened via urls. Having to press "OK we know our device doesn't have a location" every time a form is opened is pretty cumbersome. The workflow we use is valid for us because it forces the survey to be associated with an existing point. In our case it forces an ADA ramp inspection to be associated with an existing intersection point. The user does not have the option to change the geometry of the survey which is what we want. So there is no need for a device location and the survey should be usable on a device that does not support device location. Since this is a Workflow ESRI suggested three years ago, I would hope the developers would be a little less dismissive of the end user that has been using the product this way for a couple of years as to require the end user to put in an enhancement request for an issue their updates took away. There are plenty of mobile apps out there that warn you of no device location without making it so obtrusive to the workflow. For now we have a work around to use older versions of Survey123. Thanks, --joe ... View more

Hello Phil, Thanks for your reply. In regard to your statement "As all feature collected with Survey123 require a location (geometry is required)", our workflow is that we calculate the geometry by passing in to the Survey123 form a latitude and longitude from a url or by using a lookup table to get the latitude and longitude as described in this ESRI post from 2016 (https://community.esri.com/groups/survey123/blog/2016/06/08/calculations-on-geopoints). Therefore, we do not need the device location. We are opening the survey123 form from a url from the popup of a Web App builder app which passes In the latitude and longitude or a reference to a lookup table with a latitude and longitude. This is primarily done from Windows 7 desktop computers so I don't know if they have a location services setting and I don't think we should have to turn them on if they are not already on just to use Survey123. Also, wouldn't another workflow be to allow the user to choose the location from a map without having the device location turned on? Let me know if I am missing something. Shouldn't Survey123 support a workflow where the location is entered independent of the device location without receiving a system error message every time? The scenarios above describe two such workflows. Thank you. --joe ... View more

Hello Phil, I have the same issue as Jennifer with the "Unable to Connect" message appearing even though Alerts are turned off. I tried your suggestion and downloaded the Beta version (3.655B), deleted the settings files and I get the same results. I am using Survey 123 on a Windows 7 Desktop computer. Is there a previously released version I could download from somewhere? We have been using a retired version 2.3.29 for the last couple of years and just started having issues so need to upgrade. Thank you. --joe ... View more

After consistently receiving a "Staging Failed" error trying to publish the Export Web Map tool as a Web Tool, we can finally say we have succeeded in sharing a web tool to ArcGIS Enterprise 10.6 using ArcGIS Pro 2.1. We checked this article about the "Staging Failed" error, but none of the listed causes seem to fit our issue. https://support.esri.com/en/technical-article/000015108 The ultimate solution in ArcGIS Pro 2.1 was as follows: a. Run "Export Web Map" Tool. b. Share the results as a Web Tool. This is where we get the "Staging Failed" error. c. Run "Stage Service" using the sddraft file from the "Share as Web Tool" step above. The draft file can be found under the current user name’s ArcGIS Pro sharing folder for the last process shared. (C:\Users\<USERID>\AppData\Local\ESRI\ArcGISPro\Staging\SharingProcesses\<JOBID>\<ToolName>.sddraft) d. Run "Upload Service Definition" using the sd file generated from the Staging step above. e. If not done as part of the publishing process, share the print service in Portal. It might be helpful to note that according to this article, Web tools can only be shared with ArcGIS Enterprise server 10.6 or later ( http://pro.arcgis.com/en/pro-app/help/analysis/geoprocessing/share-analysis/what-is-a-web-tool.htm). Also, I believe ArCGIS Pro 2.1 is the first version to have the Export Web Map tool so maybe this will be fixed in future releases. Incidentally, the only reason we used ArcGIS Pro instead of ArcMap 10.6, is that when we publish the Export Web Map tool with ArcMap 10.6, our web app builder print widget fails when we use that service. We traced this issue down to the print service published with ArcMap 10.6 having trouble with the print widget submitting "visibleLayers":[-1]  when a layer has no visible layers in the map. It works fine on a print service published with ArcMap 10.3 but not 10.6. I hope this helps. --joe ... View more

We finally got a chance to try this out and it works great for us, just what we needed. Thanks for implementing this so quickly. We chose to use the google Universal Link (https://developers.google.com/maps/documentation/urls/guide) in a custom popup. This opens a window within Collector with the street view displayed and the ability to pan and zoom and open in Safari. The link we use in the custom popup is: <a href="https://www.google.com/maps/@?api=1&amp;map_action=pano&amp;viewpoint={latitude},{longitude}" target="_blank">Street View</a> We tried the "comgooglemaps://" structure also, but it seems to require the Google maps ios App to be installed first to work. The universal url will open in browser or google map app. Thanks again, ... View more

Of course I figured out the obvious solution 30 seconds after I submitted my question. Apparently I had not shared all the layers in the map properly and that was the issue, not downloading the basemaps. Interesting that I had to try to download the basemap to find this out. Solution: make sure user has access to all layers in map. With Kind Regards, --joe ... View more

I get the same message when trying to access basemaps as a "Non-administrator". “You do not have permissions to access this resource or perform this operation” I noticed it first on basemaps that had been sideloaded (.tpk) but tried downloading an ArcGIS Online basemap and got the same message.  To top it off, I had previously downloaded these offline basemaps on these same devices with the same user names a few weeks ago and they sat in a drawer never being used. Now when I try to download either the same or new basemaps I have this issue. Also, I cannot delete the basemaps from the device, because when I go to Manage, it says the basemaps are being used in 3 maps.  We are using iPads with Collector version 17.0.3. Any help will be appreciated. With Kind Regards, --joe ... View more

Thanks, James. Just to be clear. Is there any way to set up a survey with the new 2.0 release that would allow us to edit an existing survey and send it without error? If there is a way, I would like to try it. If not, I will wait for the next release before trying this option. I really like what I have seen so far of the interface to edit existing surveys and this feature is really important to current projects we are developing, so I hope there is a way to get started on it soon. Thanks again. --joe ... View more

Thanks for your response, Michael. This works great. I have another related question. Is there a way to set up the Inbox map to use the same settings as the Survey's map or is there another way to set up the Inbox map settings? When I try to use the inbox map it starts out zoomed way into the middle of the Atlantic ocean. When I press Home it goes to Melbourne Australia which is nowhere near my location. Thanks again. --joe ... View more

Hi James, Is there a work around for this to use before the next release? I tried adding the GlobalID field as a readonly field in the survey, but I still get the same error. I am able to add a new survey point and it submits okay, it is just when I try to edit an existing survey point that I get the error. Thanks, --joe ... View more

I got frustrated working this same issue about a month ago and just got back to look at it. Glad I saw your post as it motivated me to try to track this down again. What I found out is that there are some specific rules in Survey123 for related tables and as far as I can tell they are not published anywhere. The rules are: The relationship fields must be GUID fields with the same name in the parent feature layer and the child table. The GUID field cannot be the GlobalID field. The label name of each side of the relationship must be the same. Following these rules I created the attached relationships from your example. I created a GUID field called parentguid in both the parent feature layer and the child tables. Then I created the relationships for each table to the feature layer and labeled both sides of the relationship with the same name as shown in the attached labels image.  When the survey form is created, the parentguid field does not appear in the spreadsheet or on the form. But, when a new inspection is created with the form, the parentguid is apparently automatically  filled in with a GUID.  When records are added to the tables in the form, their parentguid fields are automatically filled in with the parentguid from the inspections layer. I verified the results in the REST service and the relationship and related records are there, so I think this is right. It sounds like ESRI may be planning to support GlobalID's directly in a future release. I pieced together the solution from the following cryptic post and help file: https://community.esri.com/thread/192312-survey123-error-global-id-based-relationship-requires-support-for-applyedits-with-globalids https://doc.arcgis.com/en/survey123/desktop/create-surveys/survey123witharcgisserver.htm#ESRI_SECTION1_147B3E0089E7446290615D3F1D139231 The post says  "Survey123 does not work with GlobalID, GUID relationships for related tables (repeats) with Federated Servers yet. It is in the works but is not there just yet. I believe it may be available in the next release in April?? The repeats use ParentRowID/RelatedParentRowID for the repeats." and "Yes, there are a few caveats with relationships.  From your description, it sounds as if the *relationship* does not have the same name from the parent and child tables - currently Survey123 assumes the relationship name is the same" The help file says: "repeats cannot work with related layers or tables unless the relationship uses a GUID field for the relationship in the parent layer"   It is hard to understand why this is not documented somewhere obvious where we can use it. This is pretty much the traditional model for data collection in the field for things like inspections. I hope this helps. ... View more

Yes, I think that makes sense. I think what is happening is that when the map is refreshed, the data from the existing feature on the host server is being filled in to the edit form fields. In the case of adding a new feature, the feature does not exist on the host server until after submitting, so there is no data to overwrite on the edit form fields. ... View more

Thank you, Morgan. By the way I tried it on an Android device and because of the different steps involved in changing field values, I did not have the same issue. Thanks again. --Joe ... View more