If you used FILE I/O commands to get measurement text from Xact, there is a completely new library of commands for Geometric Tolerancing, in which you will have to get/make a script to modify EVERY SINGLE PROGRAM to convert the commands, so that text will export to a CSV correctly. That is why I am holding out on 2020 R2. I do not have the time to undertake that monstrosity.
Naming features, alignments or dimensions as numbers has always been problematic and is not recommended for precisely this reason. It is because the assignment can not distinguish between a feature named 1 and the number 1. The way around it is to reference it as a pointer by enclosing the 1 in squiggly brackets - for example ASSIGN/V1={1}.MEAS would work whereas ASSIGN/V1=1.MEAS would not.
Naming features, alignments or dimensions as numbers has always been problematic and is not recommended for precisely this reason. It is because the assignment can not distinguish between a feature named 1 and the number 1. The way around it is to reference it as a pointer by enclosing the 1 in squiggly brackets - for example ASSIGN/V1={1}.MEAS would work whereas ASSIGN/V1=1.MEAS would not.