Comments
-
Good timing on your question. I was just sent a temporary workaround yesterday. I can confirm that it fixes the issue. No word on general availibility yet. You may try opening a case and asking for the workaround.
-
Good news, after several weeks and back and forth with support. They have finally agreed that this is a bug with 2023.1. No ETA on a fix.
-
Ivo, the case number is 01268777. The screenshot that I posted is from a fresh trial install of IPAM that I did on a new server yesterday in order to verify what I was seeing in production. Thank you for looking in to this.
