Thank you for the reply.
So the issue still exists in scenarios where previous years of DBMgr (2019/20/21) is installed alongside QB22 DBMgr it sounds like. We are able to replicate the same issue.
