That sounds like a bug which was in previous versions of the component, but is fixed now. If you update to a more current service release it should work.
That sounds like a bug which was in previous versions of the component, but is fixed now. If you update to a more current service release it should work.