15-02-2024, 05:44 PM
The VEDA Online documentation says the following:
I just happened to test this, and it seems that VEDA2.0 v3.0 no longer has a problem with Duplicate column names in FI_T tables. No error is being issued, and the rightmost non-empty value over the duplicate columns in each row seems to survive, as it was in VEDA-FE. Is this correct, and does this mean that the old behaviour of VEDA-FE (with respect to duplicate columns) has been restored? I am by no means advocating the use of duplicate columns, but it would be good to know whether it is now supposed to work or not.
Quote:First time you import a new model folder, you may need resolve three types of issues that were working OK with old veda:
◦ Duplicate column names
● Can append redundant info like ~ANNUAL or ~<baseyear> to differentiate columns. For example, if an FI_T table has two columns called “Input”, then one of them can be named “Input~2010” (if 2010 is the base year).
I just happened to test this, and it seems that VEDA2.0 v3.0 no longer has a problem with Duplicate column names in FI_T tables. No error is being issued, and the rightmost non-empty value over the duplicate columns in each row seems to survive, as it was in VEDA-FE. Is this correct, and does this mean that the old behaviour of VEDA-FE (with respect to duplicate columns) has been restored? I am by no means advocating the use of duplicate columns, but it would be good to know whether it is now supposed to work or not.