millij

Hi @anablav , Can you provide some more details on what you're looking for? As in.. What's your input and what kind of output you're looking for.

It's an interesting ask. At this moment, the current project doesn't support the nested structures. Here is a workaround that I can think of .. - Have all the fields...

@suhas-ravikumar Can you share the file you downloaded from S3? it will help in replicating the bug. Thanks

@pbacz Tested changes - they are not working for me. Request you to check the changes again. Thanks

@YaroValentine We're using apache commons-beanutils for recognizing bean methods. Hence the issue. Refer to the below link https://stackoverflow.com/questions/42244023/commons-beanutils-if-set-method-return-is-this-model-cant-get-writemethod

@iamsethi The current API `(v3.0.0)` doesn't support multiple names (or aliases). As for your case, I recommend creating two fields as opposed to creating 2 POJOs; Sample code below ```...

We don't have support for this yet. I will take it up and make it part of the coming release.

@Sand038 May I know which version of the `poi-object-mapper` are you using? Also, go through #14 issue for a little more information on the Apache POI version support. **Update:** I...

@chiragrlti At this moment, the `Reader` implementations expects **one-to-one mapping between columns and Java Class properties**. Having 2 columns with the same name doesn't satisfy the current expectation. One workaround...

Potential Solution is to allow `SheetColumn` annotation to accept Column `index` as an alternate to Column `name`. **Pro**: More flexible API, i.e., supports both Column name mapping as well as...