Latest Contributions by AmyRoust

I'm rewriting a Python 2.x script so that it can be used in Pro. I am struggling to figure out the syntax for refreshing a map series in Python. I found this page: MapSeries—ArcPy | ArcGIS Desktop, and I know there is a refresh() method, but I cannot figure out how to use it. I tried  lyt = aprx.listLayouts("AgLayout")[0] for lyr in m.listLayers("Parcel*"): lyr.definitionQuery = "JOINPIN = '201-02-0-00-00-012.03-0'" lyt.refresh()‍‍‍‍‍‍ Line 6 throws an error that says "AttributeError: 'Layout' object has no attribute 'refresh' ... View more

Working with 10.5.1, Advanced Desktop license. I've got a model set up in Model Builder that starts with a step to Delete Features from a point feature class in a file geodatabase with about 55,000 points in it. The points are deleted quickly, but then the tool sits at 100% complete for about 10-15 minutes before going on to the next step in the model. Because of the number of steps in the whole model, I am reluctant to export to Python and deal with the mess of code that is generated, so I'm hoping to brainstorm possible causes of the hangup in Model Builder. If I have to go to Python, so be it. Just looking for alternatives. ... View more

My team has three brand new iPads with Collector installed. They all do the same work – update the sign inventory in the field. We have a basemap permanently installed on their iPads, and when they are ready to go out to work, they download the sign inventory features for disconnected editing. When they come back in at the end of the day, they sync up their data. Afterward, we have them delete the features that they downloaded so that they can start fresh in the morning with a new copy of the data. Two of the iPads see this message when they go to Manage and Remove Map:   Those two iPads never have any problems with synchronization. The third iPad, which regularly has synchronization issues, gets this message:   We thought maybe the third iPad had a different version, so we uninstalled/reinstalled Collector on that iPad. When that didn’t work, we completely stripped that iPad down to factory settings and reformatted it from scratch. Still, it gives this message instead of the one that the other two get. We have that employee choose the “Remove features only” option when he gets that message. This used to work well, but for the last month, I've noticed that the replica is not being removed from the master database when they choose “Remove features only.” I could live with orphaned replicas that require manual cleanup, but this same iPad keeps throwing this error message when the user syncs his edits: And let's just make this a bit more confusing: his edits actually do sync into the associated version and we can reconcile and post with no problem. But Collector thinks that the edits did not go through. Bottom line is that I need the iPad to reliably sync with no error messages when the user comes back in from the field. I don't know if the orphaned replica has anything to do with our error messages, but I'm at a loss on what to try at this point. ... View more