Hi, Steve,

Yes, this has now been reported at 2 (looks like 3 now) other sites. It was reported to R&D and has been fixed for the next release.

In the meantime, please use DataCare to check integrity in AR as it does not exhibit the same problem.

Sorry if I didn't get back to you specifically with this information once I was finally able to determine it was a problem that will only show itself with specific data.