It appears there may be an error in the SEND Config file. Up until Pinnacle21 Community version 2.1.2, the dataset variable types seemed to match the SENDIG.
Now they appear to no longer be in alignment. This is returning false errors I believe. I noticed this case in the LB Domain, where the dataset type according to SENDIG is Num or numeric for LBORNRLO and LBORNRHI. Our LB.xpt file contains this information at the metadata level, but the validator returns error SE0055/FDAN032. Prior versions had this type as float.
Or is the issue tied to fact that this permissible column was not populated but present, even though that is a different rule, which is a warning not an error.
Pinnacle 21 uses cookies to make our site easier for you to use. By continuing to use this website, you agree to our use of cookies. For more info visit our Privacy Policy.
It appears there may be an error in the SEND Config file. Up until Pinnacle21 Community version 2.1.2, the dataset variable types seemed to match the SENDIG.
Now they appear to no longer be in alignment. This is returning false errors I believe. I noticed this case in the LB Domain, where the dataset type according to SENDIG is Num or numeric for LBORNRLO and LBORNRHI. Our LB.xpt file contains this information at the metadata level, but the validator returns error SE0055/FDAN032. Prior versions had this type as float.
Or is the issue tied to fact that this permissible column was not populated but present, even though that is a different rule, which is a warning not an error.