This content has been marked as final. Show 2 replies
There was hotfix released to address this, I believe. Check with Support.
Yeah had this before, but we have later HotFix applied and not sure why still getting this. Thought there was a work around.
I'll check with our support folks.