Latest Contributions by PeteJordan

Yes anything helped and that's the kind of thing ESRI support asked me to try as well.  And yes editing yesterday I found the projection I had when I did previous tests, the default maps I made were in WGS and not State Plane, when I realized I couldn't use some editing features I found I was in the wrong projection and switching back the issue came back.     Got on here and found that GrantHerbert posted 30mins before me discovering the same thing.  So forwared that to the ESRI team that has been in contact with me over this.   I just feel in the mean time, it's either deal with it and have multiple projections to switch back and forth depending on what needs to be done or deal with just having that missing portion at the top until it a fix comes out in another update version... ... View more

Hey Micheal, I just looked at my settings and the are exactly the same as yours.  So I can't see the redering being the issue.   I just deleted the temp cache's in the AppData as well and nothing changed (I also have Pro to clear the local cache every time I exit).   So not sure if I should do any testing on changing those redering settings as they are the same as what you have? ... View more

  This is what I just discovered and came on to report as well.  It tured out the Projected NAD 1983 (2011) State Plane I use has the issue, but WGS 1984 doesn't.  I also tried other state ones for the Projected ones and fould all the Colorado ones to have the issue, but other states as a test were fine.   I have emailed the tech support team on this bug that I had submitted with the latest update on it with the projections... ... View more

I noticed by mistake that another map that I had while testing somethings out, had the exact same imagery and that didn't have this issue.  So it seems that some maps with the imagery may be fine and others are corrupted.  Copying over the imagery to the map showing the issue, didn't solve the problem.   I ended up having to just copy the map with the good imagery, remove all the layers from that copy and then copy over all the layers from the original map into that new one and it works fine.   Very odd that several of us have had this issue though... ... View more

Yes exactly what I am seeing.  I just submitted a bug report for this now... ... View more

Good to know that I'm not the only one.  Hopefully someone at ESRI sees this and can submit this as a bug report... ... View more

  Yes I had a case filed and it was already brought to the lead technician working on the issue.  So far with the latest patch, it still wasn't working properly.  It was assumed it stemmed from the BUG-000177497, but it wasn't verified at all that it was part of that bug or something else like a previous update.   Either way, I just continue to turn off Nearmap when I need to do an Attribute Transfer as 3.5.3 patch didn't fix it... ... View more

  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