Thank you for bring this to our attention, I do see that this unexpected behavior has been reported to our development and will be fixed in a future update of the ProSeries program.
View solution in original post
