Latest Contributions by AdminAccount2

‎10-06-2021

Thanks for that reply. I'm testing this process using AGOL instead of Portal, but it sounds like exactly the same issue regardless. You indicated this process used to work fairly recently - I'm guessing it broke sometime around September 16, the last major AGOL update by ESRI - does that sound about right? If so, maybe we can pinpoint the issue to something that occurred in that last ESRI update. I'm working with tech support and will post updates to the issue as received.

‎10-05-2021

Thanks for posting that. I recreated that flow and everything works - except if the report template contains a geopoint type question, then it fails with: ["An error occurred when rendering by the report engine. Failed to print map for `$map_geopoint`. waiting for function failed: timeout 180000ms exceeded"] If I remove the geopoint question from the MS Word feature report template, then it works fine and generates the report from the Flow API request. When the geopoint question is included, the report generates normally without error from the Survey123 web site, but fails if called from the Flow API. I have already opened a support request with ESRI on this issue, but so far we have been unable to resolve this. The query works and everything is returned, but it seems like it cannot access the map used for printing the geopoint in the MS Word feature template. We have tried many things to to resolve this, including adding the webmapItemId and mapScale parameters and trying different formatting of the request within Flow and also using Postman, but nothing seems to work when a geopoint question is included. Just wondering if you or anyone else has tried including a geopoint question in the MS Word feature report and then using the API request from Flow to generate the report. Has anyone successfully done this, had similar issues or found a way to resolve this problem? I'm testing with a report template that is very basic - one question and one geopoint... no repeats or anything.

‎10-05-2021

Hi Zoltan, Thanks for posting that. I recreated that flow and everything works - except if the report template contains a geopoint type question, then it fails with: ["An error occurred when rendering by the report engine. Failed to print map for `$map_geopoint`. waiting for function failed: timeout 180000ms exceeded"] If I remove the geopoint question from the MS Word feature report template, then it works fine and generates the report from the Flow API request. When the geopoint question is included, the report generates normally without error from the Survey123 web site, but fails if called from the Flow API. I have already opened a support request with ESRI on this issue, but so far we have been unable to resolve this. The query works and everything is returned, but it seems like it cannot access the map used for printing the geopoint in the MS Word feature template. We have tried many things to to resolve this, including adding the webmapItemId and mapScale parameters and trying different formatting of the request within Flow and also using Postman, but nothing seems to work when a geopoint question is included. Just wondering if you or anyone else has tried including a geopoint question in the MS Word feature report and then using the API request from Flow to generate the report. Has anyone successfully done this, had similar issues or found a way to resolve this problem? I'm testing with a report template that is very basic - one question and one geopoint... no repeats or anything.

‎09-23-2021

The .csv file is loading correctly now - user error on my part.

‎09-23-2021

Also appears the form has issues loading the associated .csv file from the media folder when trying to edit: Error appears after selecting edit

‎09-23-2021

I know <body bgcolor="#FBBCBC"><font color="black"><b>Mission Request</b></font></body> is another one that doesn't work any longer.

‎09-23-2021

Thank you for the reply James. I can easily change the HTML, but that's not the major issue. I've opened up a support ticket for the other issue regarding the inability to edit a form in the web app (following the Sept 16 update) when there is a value in the body::esri:visible field. Any idea what change to the web app may have caused this? I've attached screenshots and examples to my support case here: https://my.esri.com/#/support/cases/02897569

‎09-22-2021

I've noticed the same thing - the html syntax is no longer respected. But, worse than that it appears in this latest version it no longer respects the value of the body::esri:visible field. It appears these fields are visible, but no longer editable. I have values in there to hide some fields in the field survey, but they need to be visible and editable by approvers in the web form. They appear as visible, but not editable in this latest version of the web form.

‎09-21-2021

I republished my data from our org's enterprise geodatabase via a SQL Server connection. This resolved the issue.

‎09-15-2021

Hey all, I have a simple arcade expression that calculates an area name string to a point that falls within that area. I'm trying to publish the feature service from Pro 2.8.3, to Portal. The two datasets (point, and poly) are registered datasets on Server 10.8.1. var outerGeom = FeatureSetByName($datastore, "Test_Areas", ["name"]) var featureWithin = Intersects(outerGeom, Geometry($feature)) if(Count(featureWithin) > 0) { var layer = First(featureWithin); return layer.name; } else { return null; } I am following the instructions on Share Datasets with Attribute Rules. At step 5, under "Share datasets with attribute rules", it mentions that I have to publish the referenced registered data as a feature, in addition to the map image layer. Am I interpreting that correctly? When I attempt to publish the two features as a web layer, I get an error, suggesting that referenced data is not compatible. To be clear, these datasets are not yet feature services; they reference data stored on the server. (same is true with the polygon feature) The referenced data store points to a folder on the server, where my FGDB (along with several other active registered FGDB's) is/are contained. Can someone help me to understand what it is that I'm doing wrong? Thanks in advance... -MG

‎08-04-2021

Hi Zhifang, I appreciate you keeping me updated on any progress. The ESRI Support Ticket information is: Esri Case #02860695 - AGOL Survey123 Outage not reported on ESRI Health Dashboard

‎07-30-2021

FYI - ESRI Support was helpful and responded to the case I opened with this reply: "I can confirm that there were performance issues with generating reports in Survey123 yesterday from 3:15 PM to 7:00 PM EDT and I have attached this issue to our case. In regards to the performance issue not appearing in the ArcGIS Online Health Dashboard, currently Survey123 is not a product listed in the Health Dashboard. However, I communicated your feedback with out internal resources and they have included your situation in a planning document for future improvements to the ArcGIS Online Health Dashboard. We greatly appreciate your feedback and I completely understand your frustration with not seeing a public explanation for the issue your organization was experiencing. Your feedback will be a great help in improving our communication moving forward and I believe will help many users."

‎07-30-2021

Yesterday (2021-07-29) beginning around 3pm EST all the Survey123 submissions through Integromat that generate feature reports began failing due to a time out error. This was not a single survey, but multiple different surveys using different feature reports. I went directly to the Survey123 web site and tried creating the reports manually from there. That failed too, and continued to fail all the way up until around 7:30pm EST when it began working again. There were 23 surveys backed up in the Integromat queue. Clearly there was an issue with one of the hosting processes at ESRI that was failing to process these feature reports from the Survey123 web site since trying to generate any of them manually from the web site failed. There were (3) reports that were skipped – never even made it to Integromat since the trigger never executed because the Survey123 site must have been unreachable. I had to identify and process those ones manually. Yet, the ArcGIS Online Health dashboard showed all green – no issues - and still does the following day. That dashboard seems to be pretty much useless. It would be nice if it actually identified issues when they happened in real-time, but even after the fact when they don’t show up is even more frustrating – like there never was an issue. I'm opening a case with ESRI on this issue to hopefully generate some action. We have many people depending on these reports and we hear about it immediately when they don't receive them. It is understood there will be outages and problems from time to time, but having no acknowledgement of the issue by ESRI so we can pass along the information while waiting for a resolution is unacceptable.

‎07-27-2021

Hey there, Following up on another post regarding grouped layers in Maps Beta. It seems as though when I use the map that was created in Maps Beta (including grouped layers) in Dashboard, only the non-grouped layers appear. I am using ArcGIS Enterprise 10.8.1, is this functionality supported? Tagging @SandraLuken1 & @JShi_EsriStaff for visibility. Thanks! -MG

‎07-26-2021

Thanks Phil. That would work for some people, but many of them would either forget to do that or not want to do that because they need to be connected for other reasons. The ONLY way to make this work reliably is to take the responsibility out of the users hands and force the issue programatically. We cannot rely on the field people to do this on a regular basis. In the office world it seems like a simple solution, but in the real world with hundreds of non-technical people using this app it's just not going to happen. Hopefully there will be a better solution soon.

Online Status	Offline
Date Last Visited	Wednesday

My Ideas

Latest Contributions by AdminAccount2

Re: Generate Feature Report in Power Automate

Re: Generate Feature Report in Power Automate

Re: Create Feature Report in Microsoft Flow - Power Automate

Re: Editing submissions in Survey123 Website appears different

Re: Editing submissions in Survey123 Website appears different

Re: Editing submissions in Survey123 Website appears different

Re: Editing submissions in Survey123 Website appears different

Re: Editing submissions in Survey123 Website appears different

Re: Error 00134 - Sharing Feature Class with Attribute Rules to Portal

Error 00134 - Sharing Feature Class with Attribute Rules to Portal

Re: No notification when Survey123 web site is not functioning

Re: No notification when Survey123 web site is not functioning

No notification when Survey123 web site is not functioning

Dashboard not supporting grouped layers

Re: Survey123 'username' field is <Null>

Re: Automate overwrite web layer, feature class

Make Categories Required as an option for every it...

Re: ArcGIS Assistant Beta (tool for managing conte...

Re: Info Summary in Experience Builder?

Re: Can you force the delete or update of a survey...