Latest Contributions by daveostrander

Hello @IsmaelChivite I have a straightforward question that I hope you can answer. I have built an ArcGIS Enterprise custom connector in Power Automate using the Esri guide. I am still at 10.9.1 for the foreseeable future until we can migrate/convert all of our services, scripts, and mxds, so it wouldn't appear that the new Enterprise connector is supported. So my question is, does the custom connector ever expire and require manual reauthorization? I am only using it with trigger-type flows that use webhooks from the Survey123 website. Thank you for any help you can provide on this! dave o. ... View more

Hello @SeanKMcGinnis  At this point in my testing, the token on my get surveys action query connection has finally expired (elapsing the 20,260-minute mark), and as a result, my recurrence flow fails with a "missing token" error. So, it would seem that setting up a recurrence flow to query the connection to keep it alive doesn't seem to have panned out for me here. However, my trigger-based flows that run when surveys are submitted using webhooks from the survey123 website still function as expected even though they have also expired (showing the survey item ID instead of the survey name and not displaying dynamic content). This development is promising! So, I think I am only down to one question: Will my custom ArcGIS Enterprise Connector work indefinitely as long as my flows are only trigger-type flows using webhooks? I guess the next test for that won't be for 90 days when the refresh token will max out (if I understand that correctly). I'd prefer not to wait that long to find out, so any guidance you can provide on the expiration of the ArcGIS Enterprise custom connector would be greatly appreciated. Thanks in advance! ... View more

Hello @SeanKMcGinnis   Since my last post, I have done some further research into OAuth2. From that, I have come to the understanding that performing the authorization and token requests in a flow will not work to keep my ArcGIS Enterprise custom connector alive because a flow produced in this way would require credentials to be entered manually at the redirect page. Instead, this workflow is really what the custom connector does for me on its own. So, my question now is, will the ArcGIS Enterprise custom connector refresh itself indefinitely (whether or not any flows run), or do I still need to have a recurrence flow that runs daily, which queries the connection using an action type flow? In my case, the flow I set up queries all of my published Survey123 surveys. So far, in my week or two of testing, I haven't seen the custom connector lose connection, requiring a manual sign-in to reauthorize it. However, even losing connection at 90 days would be bad for a production workflow where the public submits surveys at will. Again, thank you for any guidance you can provide on this. ... View more

Hello @SeanKMcGinnis   I am trying to understand the rules regarding tokens for our current connection. Unfortunately, we are still at 10.9.1 for our ArcGIS Enterprise and will likely need to be at that version for some time. However, I did create a custom connecter using the Esri technical article that works well with Survey123 and ArcGIS Enterprise Portal (I know it's not supported exactly). I am just now getting back to testing/working with this connection, and if memory serves correctly, I have had flows where the token expired on my trigger (no longer showing dynamic content and listing the item ID instead of the survey name), but it still functioned when surveys were submitted. So my question is a multi-fold one: will a custom ArcGIS Enterprise connector connection expire (if so, how long before that happens), and within my flow, can the trigger expire and continue to function? Also, you mentioned a workaround to keep connections alive. You stated: "If the flow has not run within the duration of your refresh token timeout, it will fail. The way I have been getting around this is I have a scheduled flow for each of my connections that runs daily to query against a specific feature layer. This forces the refresh token to be refreshed before it times out, preventing me from getting unexpected connection issues." I built two scheduled flows in an attempt to follow what you were laying out above. I have a scheduled flow with my custom connector connection, which queries all my published surveys. The other scheduled flow makes an HTTP POST request to generate a token, parses the JSON to retrieve the token as dynamic content, and makes an HTTP GET request to query all of my published surveys. That one doesn't work because the token I get doesn't seem to work with the header's Authorization: Bearer <access token> scheme. Assuming both are working, would either of these scheduled flows have the effect of keeping the custom connector alive? And where does one get a Bearer access token if it differs from a portal-generated token? I am just seeking as much clarification as possible since there seem to be different types of tokens and connectors/connections at play. Thank you for any guidance you can provide with this. ... View more

@NateHollenbeck I am not aware of a way to do that, but the most straightforward fix is to make your coded domain values the same as your labels. I believe using codes as opposed to the full value was primarily for saving space on disk when that was a more significant concern than it is today. You could then use field calculate to update your existing values to the new ones. ... View more

Not only the solution I was after but served on a silver platter!!! Thank you @JohannesLindner  ... View more

It doesn’t appear to be possible on mobile. I will update/correct  tomorrow. Thank you for the tip. ... View more

Hi @IsmaelChivite,   I am having an issue when attribute values contain a single quote, such as a person's last name (e.g., O'Brien, O'Malley, or O'Hara), which is then interpreted as the end of the string, and all remaining values being passed are truncated (BUG-000118152). The lost attributes can result in orphaned records in my case since the Survey123 forms add records to a related table. That table depends on the feature's GlobalID being passed to ensure relationship integrity. I could move the GlobalID to the first position of the URL scheme, but then I wouldn't be able to tell that data was incorrectly passed into the related table. So, the lack of a GlobalID foreign key in the related table allows me to search for and manually correct these issues. The URL scheme I am using looks like this:   Collector popup URL scheme link: arcgis-survey123://?itemID=<SurveyItemID>&field:permitnumber={permitnumber}&field:name={name}&field:address={address}&field:email={email}&field:permitguid={GlobalID}   To mitigate the behavior, I have replaced the handwritten link in the popup with an arcade expression that uses URL encoding functions to ensure my URL scheme is formatted correctly. Fortunately, this also appears to have resolved the issue with single quotes in the attribute values. Unfortunately, however, this now introduces a far worse problem. All of my attributes get passed except the GlobalID field needed to cement the relationship. As a result, every record created with Survey123 becomes an orphaned record, obviously not the workaround I had hoped to develop. The Arcade expression I am using looks like this:   Arcade expression replacing previous manual URL scheme: var urlsource = 'arcgis-survey123://?' var param1 = {    itemID : '<Survey ItemID>' }; var param2 = {    permitnumber : $feature.permitnumber }; var param3 = {    name : $feature.name }; var param4 = {    address : $feature.address }; var param5 = {    email : $feature.email }; return urlsource + UrlEncode(param1) + '&field:' + UrlEncode(param2)+ '&field:' + UrlEncode(param3)+ '&field:' + UrlEncode(param4)+ '&field:' + UrlEncode(param5)+ '&field:permitguid=' + $feature.GlobalID;   Which returns this: arcgis-survey123://?itemID=<SurveyItemID>&field:permitnumber=21-F006&field:name=Ariel%20and%20Nancy%20Smith&field:address=555%20South%20SomeRoad%20Road%2C%20Dwight&field:email=someonesemail45%40yahoo.com&field:permitguid={B3F2E6C2-4AE0-46DB-8648-E3C563A32ECA}   The URL looks good to me, but as mentioned previously, it never dynamically passes the GlobalID. At this point, it appears that Survey123 might not be interpreting arcade expression URLs correctly. In addition, I see odd behavior beyond the GlobalIDs being truncated. For example, the arcade Replace() function works intermittently. Initially, my idea was to replace all single quotes with backquotes dynamically. However, this didn't seem to work when the single quotes existed between lower case letters.    At any rate, do you or does anyone here have a solution to using Arcade to build the URL scheme without dropping the GlobalIDs? I have a support request open on the issue, but I wanted to reach out directly to the GeoNet community to see if there might be a solution to this that I am somehow missing. I am using data stored in SDE, ArcGIS Enterprise 10.8.1, and the latest Surve123 and Collector apps, 3.13.229 and 21.0.4, respectively. ... View more

No problem, Steve. I'm happy to share any updates that I am made aware of. Better yet, hopefully, Esri will beat me to it and post that news for the community once it is available.   ... View more

For those interested, below is the emailed response I received from Esri: "Thanks for reaching out… We will soon be processing and compiling the 2020 Census data for release with the Esri Redistricting solution. For now, we anticipate the final release of the data and software to happen during the first half of September. With our Esri Redistricting SaaS solution, we have to coordinate the software release with the 2020 Census data release to ensure continuity in the solution. This will be seamless to our customers and please look for email communication as the release time approaches." ... View more

Hi Ismael, To combat the no attachments uploaded issue in Power Automate, I do a conditional check using the empty function to check if attachments exist.  If that results in true then I do the email with attachments or add attachments to another feature service, etc... If false, send without.   Maybe this would be useful. -dave o. ... View more

I never did find a way to set the transformation procedure. I am using the Project ArcGIS REST API operation available at the Geometry Server service to get around this. Using webhooks payload data and an automation services platform allows the Project to happen on the fly, which can then be captured using Parse JSON action, which then gets fed into the applyEdits operation to add the point in the correct coordinate system at the correct location. ... View more

Thank you for implementing this!!! -dave o. ... View more