Hello Raymond, in researching this issue, I was able to find a similar issue that is and was fixed in V2. However, as you know this issue exists in V1. I was able to recreate and verify the issue that you are seeing. I documented it and though there is not a target date for when this issue will be addressed, our developers have been made aware of it. Thank you for reporting this and we do appreciate your feedback. …Jack
