Latest Contributions by ScottStopyak

Yes! This got my connection speed down to 3 seconds! Thank you! ... View more

Update: As suggested above, for me removing the gp history from db worked wonders.  We also have this issue. We're currently running 10.7.1. The initial connection to the MSSQLSERVER DB (LGIM schema) takes 12 seconds. After that, opening a  feature dataset takes an additional 7 seconds. It isn't a show stopper but the problem didn't exist in the 10.3 era. I've used UNC and DNS in my connections and there was no difference. I also tried compressing and rebuilding indices. That was interesting because the initial connection actually took 2 seconds longer but opening a feature dataset took 2 seconds less, so it was a wash.  QGIS connects relatively quickly and is opening each dataset from the get go in about the same amount of time arc takes to make the initial connection. SSMS opens the database in under a second. I suspect it isn't a database issue. It is something that was introduced in later Arc versions (maybe at 10.5). Maybe a look at release notes between 10.3 and 10.5 might provide some insight. IDK. Further testing showed that if you recursively list all feature classes in the database (regardless of whether or not they reside in a feature dataset) using arcpy it takes 41 seconds. So apples to apples, QGIS is connecting to these twice as quickly and SSMS is exponentially faster. I'd be kind of interested in seeing a comparison between 10.3 and 10.7. I might be curious enough to try it. I'll post results here if I do. The takeaway for me is that it's looking more and more like Arc is responsible for the delay.  Here's a script to test for yourself. The first time you run it, it will take awhile. Run it again right after that. It will run twice as fast because the initial handshake has already been made. At the very least, you'll be able to quantify the initial connection lag for your specific DB so you'll have a baseline. import os, arcpy, time gdb = r'%AppData%\ESRI\Desktop10.7\ArcCatalog\yourconnection.sde' start = time.time() arcpy.env.workspace = gdb datasets = arcpy.ListDatasets(feature_type='feature') datasets = [''] + datasets if datasets is not None else [] for ds in datasets:    for fc in arcpy.ListFeatureClasses(feature_dataset=ds):       path = os.path.join(arcpy.env.workspace, ds, fc)       print(path) end = time.time() elapsed = (end - start) print(elapsed) ... View more

Maybe Qfield if you're running a supported database. I think it has online and offline modes. You might then need to setup a python script to get synced to portal. The Leica software works ok for me. I dropbox the data from the field. If you really wanted to you could just dropbox it to a pc and have a python script running that sniffs your dropbox folder and if there is new data, performs a sync task. That's kind of a long way to go though unless you're good with python and enjoy tinkering with automated tasks. One caveat though is that the OS on the Zeno is so old it might not support modern apps. Even if it does, they likely won't be in the Amazon app store. There were more bad decisions made with the 20's design than a bachelor party in Vegas. ... View more

I love this idea. Currently, when building an app I use a URL redirect from our own web server. That works for keeping links the same on our page but it doesn't help for folks who have visited the app and then bookmarked it.  ... View more

Hi Graham, Having been down this road, the best solution for us was to use a GG04 smart antennae instead. The second best route is to use the Zeno with the Leica software instead of Collector. It now has the ability to add AGO layers though I'm not sure if those are directly editable. They might be. Even when the TLS proxy fix was configured, we had some performance issues trying to use Collector. There's an ArcGIS add-in available to push your feature classes' schema to Leica, if disconnected editing is an option. I'm a little disappointed that Leica is still selling these units. The 3G modem isn't really viable anymore and using Collector is pretty much a no-go. Hit up Jason Hooten from Leica, he can probably offer some advice and alternatives. ... View more

Thanks for that. Much appreciated. I'm not all that familiar with arcade yet so I'm thinking the best approach for me is to add a previous count field to the hosted feature class. Next, I'll start doing my edits in Pro rather than on AGO directly so all edits are sent simultaneously when I save them. Before I do my daily edits to update the current counts, I'll just do a field calc on the previous count field, pushing the current values over. Then I update the current case counts. The indicator should then (in theory) work because I can provide an attribute value as a reference. Takes a few more seconds to do it that way, but it should be foolproof, I hope. ... View more

Thanks. That could work if I can conjure an expression that'll calc the difference between the most recent and second most recent rows. Maybe create sorted lists in python and grab the first two values and subtract them? Does that sound about right? ... View more

Has anyone successfully gotten the indicator previous value reference to work right? It keeps giving the current value as the previous value. In my dash, I have data that gets updated once daily. When the data is changed (edited right on AGO) the indicator value changes. Unfortunately, so does the reference and it reports the new value as the previous value. I saw a bug out there about this and fixing it is listed as "not in the product plan". ... View more

I figured out there's a bug in the previous value reference within the indicator widget and fixing it is "Not in current product plan". The data that would be easiest to use is hosted on AGO so a scheduled task seems unlikely without getting into a lot of API stuff. Another dataset is hosted from an internal server that could maybe be query layered into the map service as a table. I was looking for more of a "set it and forget it" solution like the indicator would be if they'd fix it. Out of curiosity though, what kind of field calc would be needed? Would it be a one time thing or would it have to be recalculated every day? ... View more

The previous value setting didn't work for me after all. The data changed but the percent change remained zero.  ... View more

Thanks, Xander. I think I can tease out the most recent report using max(date) but then I need to compare it to the second most recent report. Since I can't just say "yesterday" (reports don't happen every day), I'm stuck there. I imagine it must be possible to sort the dates somehow and choose the second most recent to use as a reference to compare to the most recent. I just can't seem to figure out how that would be accomplished in arcade. Maybe I have to do this calc on the backend with Python? I was hoping to avoid schema changes though, if I can.  Update: Now I see what you mean with the indicator. It has built in field {} calcs that refer to the previous value. That in conjunction with conditionally formatting for increases and decreases will work fine. Thank you! ... View more