No worries, I got a mixed up myself. So, the CL actually is not the fix, but it is the CL that created the problem.
Earlier in this thread:
“it work flawless using 5.0 or less”
So if you needed this functionality ASAP, you’d need to revert the CL/changes. (I’m assuming that since it is being discussed on the UDN the devs are aware and would expect this to be fixed in 5.1.1 or 5.2.)