Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Automatic/Default column name extraction from excel #5084

Closed
anandansh007 opened this issue May 28, 2024 · 0 comments · Fixed by #5098
Closed

Automatic/Default column name extraction from excel #5084

anandansh007 opened this issue May 28, 2024 · 0 comments · Fixed by #5098
Labels
feature New feature or request
Milestone

Comments

@anandansh007
Copy link

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:
image
image

@anandansh007 anandansh007 added the feature New feature or request label May 28, 2024
@valfirst valfirst added this to the 0.6.11 milestone Jun 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants