-
Notifications
You must be signed in to change notification settings - Fork 29
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
Unpredictable behavior when change the set of "Additional info" columns #107
Comments
Hi @asivura. I haven't seen this behaviour before. |
Hi @MaximMoinat . We have to add additional records into the initial file from time to time. There is the reason why we are importing the new file and applying existing mappings. We decided to add additional columns when we imported the file and had the issue I described before. As a workaround, I added additional columns into our existing file with mappings manually with prefix "ADD_INFO:", but I think it would be great to fix it to avoid others having the same issue. It took us a few hours to understand why it is happening, and we lost some of the mapping results. |
That helps. So you are using the File –> Apply previous mapping functionality? That is indeed something that might not be tested in all scenarios. Thanks for reporting! |
Yes we use "File –> Apply previous mapping". |
@asivura Was able to replicate. The bug occurs with the applied mapping contains new codes and has fewer additional columns. The issue is that additional columns are not read from the applied mapping file. Working on a fix for the next release. |
Steps to reproduce:
We use Usagi version 1.3.0 on MacOS 10.15.7
Java version: openjdk 15.0.1 2020-10-20
The text was updated successfully, but these errors were encountered: