Latest Contributions by PeteJordan

  So it's been awhile and we've moved a dataset over from versioned to non-versioned on SDE for a few reasons.   Is the only current way (since the last part of this thread is close to a year old) to undo edits (similar to the <ctrl-z>) is to use the "single workspace edit session" and then each edit select your layer (if you have multiple, it's kind of a pain), edit one thing, if it's wrong, discard and repeat?  Or do a few edits, and if one thing is wrong, do the same and then re-do everything you just did correctly?   I know this causes problems when something might be deleted by mistake or if a feature is split and you don't see the other segments, until a bit later, you would again have to discard all edits in that session and go back and redo them again?   Or is there something else I'm missing that has been introduced since Nov 2023, that we can now use the <ctrl-z> in a "Multiple workspace edit session" so that you don't have to keep selecting the layer to edit, edit, disregard all edits if a mistake is made and repeat"?    What have other people on here been doing since for their edit sessions?  Another way is to just use a GDB and then keep importing that to SDE once inwhile so there is a full undo functionality again or go back to versioning which again we moved away from because of issues... ... View more

I'm also on 3.3.1.  I've since just enabled editing which solved my issue at least since the post was made suggesting doing that.  I now have also moved off versioned editing and don't have the issue at all because of that.  I still, however, see the STATE_ID=0 error in my notifications as usual, but since I'm not using versioned editing, I don't have any glitches from that error, but I can confirm it is still showing up in 3.3.1... ... View more

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