You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Current Quantipy logic assumes '.' only exist in grid/loop variables. This understanding is not true for field type variable especially when field may have loop variable in it.
For example following is valid in Dimensions MDD.
MyField "My top level field variable"
Block fields
{
InnnerLoop "Inner Loop variable" loop {_1, _2}
(
innermostvariable "Inner most simple variable"
{
_X "Answer X",
Y "Answer Y"
}
)
}
Above will generate column in data like
MyField .InnnerLoop [_1].innermostvariable
MyField .InnnerLoop [_2].innermostvariable
This variable name will fail 'get_columns_meta()' in turn failing overall reading of Dimensions input.
Option 1: Skip such variable : which is not the best solution but makes rest of the data usable.
Option 2: Rename Variable up front
Option 3: Change current logic to read more information from MDD XML as all required information is available in XML as such.
The text was updated successfully, but these errors were encountered:
Current Quantipy logic assumes '.' only exist in grid/loop variables. This understanding is not true for field type variable especially when field may have loop variable in it.
For example following is valid in Dimensions MDD.
MyField "My top level field variable"
Block fields
{
InnnerLoop "Inner Loop variable" loop {_1, _2}
(
innermostvariable "Inner most simple variable"
{
_X "Answer X",
Y "Answer Y"
}
)
}
Above will generate column in data like
MyField .InnnerLoop [_1].innermostvariable
MyField .InnnerLoop [_2].innermostvariable
This variable name will fail 'get_columns_meta()' in turn failing overall reading of Dimensions input.
Option 1: Skip such variable : which is not the best solution but makes rest of the data usable.
Option 2: Rename Variable up front
Option 3: Change current logic to read more information from MDD XML as all required information is available in XML as such.
The text was updated successfully, but these errors were encountered: