That’s interesting because I got a notification that it was fixed and would be available in build 2463. Do you have a bug report number?
Rob
Hi @Rob Miracle,
You’ll notice in my first posting that I found this issue started at build 2015.2599, which from my understanding would be after 2463.
Could you be thinking of something else?
Case 40687
I just looked up the bug and there was a note that your bug is the same as the one I reported. I had a typo above… It should read: 2643 and above, not 2463. My dyslexia kicking in (or bad typing skills).
Rob