Latest Contributions by PeteJordan

Yes I had tried that, the issue is it wouldn't even display the class at all under the Graphic subheading.  All fixed if I used Maplex which I am now using for other reasons.  I just didn't realize it was not enabled prior... ... View more

  This was what I was looking for and making me not want to use Maplex... ... View more

Yes I know about the labels not being turned on will do that and give out the warning, at least in Annotation.  The issue is the labels show up during the processing, they also create the class layer, and then when the process is done, the labels are just gone.     It might have something to do with not using Maplex, if I enable that it seems to work.  Maybe that was the issue, even for simple labels.  I have tested out the issue in a test database and found the issue in that as well, either that, or it just seems like that's the problem and it's some underlying issue with not having the Maplex enabled.  I'll just make sure that's always enabled then and see if I encounter the issue in the future... ... View more

There is already a bug report submitted for it, so no need for the Ideas as it should be working as it did prior to 3.2... ... View more

@Bud, yes I often am getting corrdinates from places like Google so haveing to re-arrage them was always a pain to do with the extra steps to make it work in the Go To XY tool.  I also like how it just makes another pane on the side of Arc that I don't have to search for.  If I have my Attribute Editor up in the bottom as I often do, I have to move that, to move the Go To XY tool to a visible space on the map.   So it's now I don't have any use for that tool anymore since the Locate tool does everything better and much more efficiently...  ... View more

@silverberrysea I have actually been using the Locate now for quite some time as I find it doing exactly what I need and much easier to use.  I've actually unbound my GoTo XY and just use Locate now... ... View more

Thanks, I couldn't remember if I had done it or not, but I couldn't figure out how to remove it at all if it was me (which I guess it was)... ... View more

At the time George_Thompson suggested it was our version of SQL that was causing the issue amd we needed to upgrade and then move to PostGreSQL.  At the time, it was marked as the solution (forgot if it was by me or George_Thompson.   Since then, there was a work around @MartinWong1 explained involving enabling the enable/disable editing as ArcMap had which solved the issue for many of us until the issue got fixed in later updates.  @joonpark also submitted a bug ticket on this as well from this thread since I hadn't done that at the time.   After that, it seems a lot more people are not even able to work even with the work around that was proposed, but since it was marked as "solved" I'm not sure I can un-solve it if I was the one that did that.  Either way, @George_Thompson might be able to Unsolve it on ESRI's end to keep this a current issue... ... View more

  With the errors popping up, that's kind of the only draw back with the work around for me.  I've now kind of trained myself to ignore the little error warnings in the bottom and/or top and sometimes if doing processes with the SDE data, I forget that valid errors might also show up in the Notifications.  So I just had to kind of train myself to only ignore them when editing the SDE data and not while doing any analysis on the data... ... View more

Thanks for that.  Our GIS admin was thinking they might contact ESRI as well, but I figured it's just all related to the same bug that was introduced in 3.2.  It just seems like a caching problem of some sort, but now after discovering the error occuring overnight at some point, makes me wonder if there is just some weird disconect with the SDE server and Pro or something? ... View more

Oh there isn't a new error.  I just meant last night I left work and everything seemed ok and the data was showing, this morning the data vanished again and a new error popped up in the error window just saying it's that same STATE_ID=0 and that was it... ... View more

Hey @George_Thompson, so we finally merged our data this week and tested it out on PostgreSQL (up to date) and after testing several things such as copying the old database to PostgreSQL, recreating a new table and appending it to PostgreSQL, I'm still getting this error.   In testing though it seemed to be fine initially before I created templates for the feature class I am actively editing, but that could have just been a coincidence.  I haven't tested it for any great length of time to see if that is for sure part of the problem or not though.     Currently the only solution is what @MartinWong1  suggested and that's enabling editing and having it set to "single workspave edit session", which is what I had to use previously before we merged the data to PostgreSQL this week...     Error code given ArcGIS Pro with the versioned data now in PostgreSQL:   Note: Last night before I left work, things were working fine without the Enable Editing checked off.  I left it over night and this morning is where I saw the error.  So it seemed to occur even without me present overnight, if that is a clue or anything? ... View more

Well ArcGIS Pro does have the ability as it does update properly if I switch the Cache mode.  That refresh that is used when switching modes just needs to be made avaliable as an option to keybind and that would solve the issue, similar to using the standard <F5> to refresh.   And yes this is done using the old ArcMap system where tables were edited directly to change measures.  We have since obtained a licence for Roads & Highways, it's just we will need to spend some time to convert our existing LRS into the new schema for it to properly work with the new tools I would assume.  So in the mean time, the quick fix would be just having access to that redraw/refresh process that happens when switching Cache methods.    And yes I agree in the future we hope to use the new LRS funtionality in ArcGIS Pro... ... View more