We started over and did new tests, and this time were successful. Now that we can reproduce the issue, we will be able to pinpoint what is causing it. Developers have already started working on it.
We will post an update in this thread when a fix (or at least a workaround) is available. Thank you for your patience.
Imported from legacy forums. Posted by Diane [Xceed] (had 832 views)