Latest Contributions by DavidRunneals2

Would be great to utilize this code in more places as well... Like being able to use it as arcg.is/shortcode ... View more

Sounds like configurable apps may see something implemented in the next AGOL update. ... View more

Re-validate your datastores and try restarting gisserver.gis/manager/site.html > Data Stores > Validate All ... View more

Per a discussion with the ArcGIS Online Team (Kelly Gerrow‌), they brought up that global IDs should be preserved where possible. In some instances (such as ArcGIS Roads and Highways and legacy applications with other systems/databases), that is not possible to do. I unfortunately can't find where I saw the best practices (help me out Kelly). We were experiencing both of what you mentioned. Some of our ETL datasets would just take a long time (and there's apparently an undocumented 2 hour timeout) while other datasets would exceed the 2 hour timeout and not sync at all. If you have a relatively small dataset, I think doing a truncate reload wouldn't be bad, but for larger ones it definitely doesn't work. We did notice that it seemed to work for a little while, but then it would fail to run, so I encourage you to do testing for at least a month or 2 before pushing your collaborations to production, so you don't have to spend a month or more undoing them like we have been doing. One other thing worth trying is splitting out your larger datasets into their own groups/collaboration workspaces so they are synced by themselves instead of with multiple datasets. We tried this and I don't think it worked very well, but you might have better success. A couple of other thoughts that came to mind... One of the esri guys on our call suggested using database hashes and comparing those to see if you really need to do a truncate/reload (Comparing Data of Two Oracle Tables Using MD5 Hash ). I also just came across this as well: How to copy or load data and preserve GlobalID values  ... View more

Per a discussion with the ArcGIS Online Team (Kelly Gerrow‌), they brought up that global IDs should be preserved where possible. In some instances (such as ArcGIS Roads and Highways and legacy applications with other systems/databases), that is not possible to do. I unfortunately can't find where I saw the best practices (help me out Kelly). We were experiencing both of what you mentioned. Some of our ETL datasets would just take a long time (and there's apparently an undocumented 2 hour timeout) while other datasets would exceed the 2 hour timeout and not sync at all. If you have a relatively small dataset, I think doing a truncate reload wouldn't be bad, but for larger ones it definitely doesn't work. We did notice that it seemed to work for a little while, but then it would fail to run, so I encourage you to do testing for at least a month or 2 before pushing your collaborations to production, so you don't have to spend a month or more undoing them like we have been doing. One other thing worth trying is splitting out your larger datasets into their own groups/collaboration workspaces so they are synced by themselves instead of with multiple datasets. We tried this and I don't think it worked very well, but you might have better success. A couple of other thoughts that came to mind... One of the esri guys on our call suggested using database hashes and comparing those to see if you really need to do a truncate/reload (Comparing Data of Two Oracle Tables Using MD5 Hash ). I also just came across this as well: How to copy or load data and preserve GlobalID values  ... View more

After switching from using FME (ArcGIS Data Interop) to using distributed collaborations to push data to ArcGIS Online, I would recommend going with FME/Data Interop every time and skip using collaborations. In fact we are going to be starting the process of reverting back to using FME/Data Interop from distributed collaborations because collaborations have some major issues that development lacked to put in the documentation, but I found out the hard way after going back and forth with support/development for 3 months which is that they don't support data that is truncated and reloaded (which is pretty much every data warehouse out there). We have data that our FME workspace has been writing at once a week (writes to SDE data warehouse), but the last time the service on AGOL was updated through the collaboration was in FEBRUARY! ... View more

Since the Dev Summit got cancelled, is there anywhere this 10.8 and post 10.8 stuff will be posted/shared? ... View more

Even more useful than this would be to make Ops Dashboard responsive, so it could work and actually be functional on mobile devices. This is something that has held us back from using Operations Dashboard when there could be users on mobile devices. ... View more