Latest Contributions by erica_poisson

Hi Zach, This is something I have tried, and it does work. I have been doing more testing between environments and noticed a few odd behaviors - maybe you have suggestions or know why this happens. When moving a Flow from Dev to Prod, I use the Export package option. I then turn off/disable to Flow in Dev. When I Import and set up the Flow in Prod, it is turned off/disabled. When I turn it on, it also turns on the Flow in Dev. I am unsure if this is expected behavior, or if it is because I have named the Flow the same thing between Dev and Prod. It also resulted in duplicate email notifications when I submitted a test survey. The only way I could think to resolve this was to delete the Dev version. However, I am unsure if this is best practice. Any thoughts? Also, when sharing a Flow with someone, I noticed that the incorrect connections were listed. I use a service account for email generation, but the dialog said it was sharing my named account credentials (which aren't even used in the Flow, although my named account owns/authored the Flow).  Thank you, ... View more

Hi @JamesTedrick , Here are some more details on what I am experiencing: 1. Open Power Automate and create a new Flow for a survey. Build out the Flow's steps and save.  2. Go to my survey and view it's Settings > Webhooks page. The webhook is there with the correct timestamp listed. It's name is just MS-FLOW.  3. Test survey/webhook - it runs as expected.  4. Go back to Power Automate and build a second Flow for the same survey; this Flow does something different. Save it.  5. Go back to my survey, view it's Settings > Webhooks page (refresh it). There is still only one webhook listed, however the timestamp has updated to when I just saved my second flow in step 3. There is still only 1 Flow, with the name MS-FLOW. There is no second flow appearing in the list.  6. Test survey/webhook - it performs the action of the second webhook (step 4) and not the action of the first webhook (step 1).  This behavior started happening in February for me. I've been trying to figure out what has happened, but I haven't changed anything in my workflow for creating webhooks through Power Automate. There has been some behind-the-scenes stuff happening with Office 365 administration in my agency and I am no privy to what they are doing/how they are changing things. I am unsure if that could be part of the reason I am experiencing these problems.  I am happy to do a screen share to show you exactly what I am experiencing. There was also someone else who said they were experiencing this too - I tagged him above in the original post.  Erica  ... View more

Hi @Anonymous User , Thank you for that tip. Once I started the service and submitted some test data, it created the definition for me. I appreciate your help! ... View more

This also works, and provides a nicely formatted time. Thank you for that. I was just digging into this blog to figure out how to format that.  ... View more

@XanderBakker  That worked! I changed the esriFieldTypeDate to esriFieldTypeString, and it worked perfectly.  Thank you! ... View more

So with this example, I see (what looks like) the same result in the console, minus spatial reference info: Use Console Function to output messages. {"fields":[{"name":"EQNum","type":"esriFieldTypeString"},{"name":"InspecDate","type":"esriFieldTypeDate"},{"name":"PtStatus","type":"esriFieldTypeString"}],"geometryType":"esriGeometryPoint","features":[{"geometry":{"x":-7997522.018099999,"y":5207172.07},"attributes":{"EQNum":"EQ2013-026","InspecDate":"2020-07-29T16:00:00.000Z","PtStatus":"Unstable"}},{"geometry":{"x":-7997970.5297,"y":5214400.591300003},"attributes":{"EQNum":"EQ1989-015","InspecDate":"2020-09-30T16:00:00.000Z","PtStatus":"Unstable"}},{"geometry":{"x":-7993994.632999999,"y":5212258.8379999995},"attributes":{"EQNum":"EQ2020-052","InspecDate":"2020-10-19T16:00:00.000Z","PtStatus":"Unstable"}},{"geometry":{"x":-8002495.5656,"y":5219019.943500005},"attributes":{"EQNum":"EQ2017-040","InspecDate":"2020-11-23T17:00:00.000Z","PtStatus":"Unstable"}},{"geometry":{"x":-7998590.2183,"y":5226627.4831000045},"attributes":{"EQNum":"EQ2021-020","InspecDate":"2021-04-21T16:00:00.000Z","PtStatus":"Unstable"}}]}     ... View more

@XanderBakker  I have tried figuring this out by browsing through GeoNet but can't find anything relating to this issue...I added the console function right before the return statement at the end, because this is still returning an empty dictionary. When I hit "Test" and view the output from the console, I see this: ["features returned",{"fields":[{"name":"EQNum","type":"esriFieldTypeString"},{"name":"InspecDate","type":"esriFieldTypeDate"},{"name":"PtStatus","type":"esriFieldTypeString"}],"geometryType":"esriGeometryPoint","features":[{"geometry":{"x":-7997522.018099999,"y":5207172.07,"spatialReference":{"latestWkid":3857,"wkid":102100}},"attributes":{"EQNum":"EQ2013-026","InspecDate":"2020-07-29T16:00:00.000Z","PtStatus":"Unstable"}},{"geometry":{"x":-7997970.5297,"y":5214400.591300003,"spatialReference":{"latestWkid":3857,"wkid":102100}},"attributes":{"EQNum":"EQ1989-015","InspecDate":"2020-09-30T16:00:00.000Z","PtStatus":"Unstable"}},{"geometry":{"x":-7993994.632999999,"y":5212258.8379999995,"spatialReference":{"latestWkid":3857,"wkid":102100}},"attributes":{"EQNum":"EQ2020-052","InspecDate":"2020-10-19T16:00:00.000Z","PtStatus":"Unstable"}},{"geometry":{"x":-8002495.5656,"y":5219019.943500005,"spatialReference":{"latestWkid":3857,"wkid":102100}},"attributes":{"EQNum":"EQ2017-040","InspecDate":"2020-11-23T17:00:00.000Z","PtStatus":"Unstable"}},{"geometry":{"x":-7998590.2183,"y":5226627.4831000045,"spatialReference":{"latestWkid":3857,"wkid":102100}},"attributes":{"EQNum":"EQ2021-020","InspecDate":"2021-04-21T16:00:00.000Z","PtStatus":"Unstable"}}]}] The console returns the 5 results I am looking for/know should be returned. I was unsure if this was happening because of the included geometry, so I removed that and tested again with the same result (console showing 5 features, but empty dictionary.   ... View more

@XanderBakker  Apologies for another question. I am trying to create a new data expression to populate a list with some basic information on these features that have no related records. I also want to pass through the geometry so I can then use the list to zoom to features in the map; this time I am maintaining the unique ID field "EQ File Number" which I hope will allow me to accommodate this.  The code below is kind of a Frankenstein from the code you helped me with the other day and some other code I used in a different data expression. It creates the dictionary, but when I "Test" it just shows an empty table. I had figured I wanted to do all of this within the first for loop, but I am not really sure. If you had a suggestion, it would be appreciated.    var p = 'https://www.arcgis.com'; var itemID_CMpts = 'xxx'; var layerID_CMpts = 0; var relationshipName = ""; var fs1 = Filter(FeatureSetByPortalItem(Portal(p), itemID_CMpts, layerID_CMpts, ['Point_Status', 'EQ_File_Number', 'Inspection_Date'], true), "Point_Status ='Unstable' AND EQ_File_Number In ('EQ2015-078', 'Eq2013-026', 'EQ2018-082', 'EQ2018-052', 'EQ2001-080X', 'EQ2003-021', 'EQ1989-015', 'EQ2002-023', 'EQ2002-045X', 'EQ2019-110', 'EQ2020-017', 'EQ2019-091', 'EQ2018-029', 'EQ2020-033', 'EQ2019-036', 'EQ2020-052', 'EQ2019-064', 'EQ2017-040', 'EQ2020-031', 'EQ2021-003', 'EQ2011-016', 'EQ2017-026', 'EQ2021-020')"); var i = 0; for (var f in fs1) { var fs2 = FeatureSetByRelationshipName(f, relationshipName, ['Point_Status_revisit'], false); var cnt = Count(fs2); if (cnt == 0) { i +=1; // create data schema var Dict = { 'fields': [ {'name': 'EQNum', 'type': 'esriFieldTypeString'}, {'name': 'InspecDate', 'type': 'esriFieldTypeDate'}, {'name': 'PtStatus', 'type': 'esriFieldTypeString'}, ], 'geometryType': '', 'features':[]}; for (var f in fs1) { attributes: { EQNum: f["EQ_File_Number"], InspecDate: f["Inspection_Date"], PtStatus: f["Point_Status"], }, }; i++ } } return FeatureSet(Text(Dict))     ... View more