This content has been marked as final. Show 3 replies
It works perfectly in 7.1.3 - many thanks!
I have the exact same problem, do you know the components involved in this fix ?
We have a big release soon and we would like to mitigate the risk from passing from 7.1.1 to 7.1.3 or 7.2.0.