Hey @remi_okarito ,
Sadly, we are still unable to reproduce this issue. It is weird though, since you are not the only one having CSV export issue using rails.
To that day, we’ve never had a reproductible setup allowing us to find what is failing, thus we were unable to locate what goes wrong.
I also did a few test for this thread, which seems to declare a similar issue, but with no luck.
AFAIK:
- The issue is not located in a wrong/bad/incorrect definition of fields in the database
- The issue is not reproductible with our mongoose/sequelize integration (The frontend request sent looks similar between our rails/js integration)
- We are not able to reproduce this issue with our live demo (Running the rails agent)
- The thread I mentioned earlier refers to
WHERE
condition added in the SQL request when generating the CSV - which does not seems related to ourforest_liana
gem.
The only place I can think of for this issue to happen would be a conflict between forest_liana
and your code, for example, a method override of ActiveRecord
shared between these two, that would lead to difference between the export.
If that’s possible, a minimal & reproductible setup would really help.
If not, maybe the SQL request executed for the export (not the count) might show something interesting, like in the mentioned thread.
I’m really sorry for the inconvenience generated by this issue, and looking forward to your answer in hope to find a fix