Sign in to ask questions, follow content, and engage with the Community
The workaround below resolved our issue:
View solution in original post