Hi, The code changes required to addres this issue have not made it out of testing and development yet. It will be solved in a future release however. In fact, we will bump this issue up in priority so it gets addressed sooner rather than later. In the meantime, as suggested in a previous response to...