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
Is your feature request related to a problem? Please describe.
When reading values from excel, Vividus considers the first row of the given range as the row that contains the column names.
In an ideal case, the first row (say A1) always contains the column names. So, if we were to provide a random range that does not start from the first index, Vividus picks the column names from the very first row of the given range. This henceforth does not replace the column names with extracted values in the story files as they are incorrectly picked.
Describe the solution you'd like
Our suggestion is to provide an option/parameter in the excel plugin that enables the users to set the row where column values should be extracted from.
Describe alternatives you've considered
Deleting the rows immediately below the column row so that the old values don't get picked up once used. This approach we don't prefer as we would like the data to be retained.
Additional context
Here are the screenshots for reference:
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
When reading values from excel, Vividus considers the first row of the given range as the row that contains the column names.
In an ideal case, the first row (say A1) always contains the column names. So, if we were to provide a random range that does not start from the first index, Vividus picks the column names from the very first row of the given range. This henceforth does not replace the column names with extracted values in the story files as they are incorrectly picked.
Describe the solution you'd like
Our suggestion is to provide an option/parameter in the excel plugin that enables the users to set the row where column values should be extracted from.
Describe alternatives you've considered
Deleting the rows immediately below the column row so that the old values don't get picked up once used. This approach we don't prefer as we would like the data to be retained.
Additional context
Here are the screenshots for reference:
The text was updated successfully, but these errors were encountered: