@RDH68 Thank you for the feedback. It was an approved workaround that was provided by our development team. Since we are working to find a quick solution to this problem, you are welcome to wait. We appreciate your patience.
