Thanks, I did try it myself with the 1.0.1 and did not have the problem and had a colleague mention to me that this issue should be resolved in the new beta. I think that the issue was not properly logged so it might not appear in the notes. If you have any more problems with it let us know.