Bug #84802 | Loses mappings when [de-]selecting first column contains names | ||
---|---|---|---|
Submitted: | 3 Feb 2017 0:56 | Modified: | 4 May 2017 23:38 |
Reporter: | Todd Farmer (OCA) | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL for Windows: MySQL for Excel | Severity: | S3 (Non-critical) |
Version: | 1.3.6 | OS: | Any |
Assigned to: | CPU Architecture: | Any |
[3 Feb 2017 0:56]
Todd Farmer
[3 Feb 2017 4:54]
MySQL Verification Team
Hello Todd, Thank you for the report and feedback. Verified as described. Regards, Umesh
[8 Feb 2017 1:19]
Javier TreviƱo
Posted by developer: Changed the behavior of how the "First Row Contains Column Names" selection affects the Data Type for columns. The value of the aforementioned checkbox controls the auto-detected Data Type for columns either by defaulting the type to a suitable one for rows 2-n (if checked), or to one suitable for rows 1-n (if unchecked). Now if the default auto-detected Data Type value is changed by the user, the overridden value remains even when changing the value of "First Row Contains Column Names". A new option called "Reset to auto-detected" was added to the Data Type field's context menu, to easily revert the Data Type value back to the auto-detected one.
[4 May 2017 23:38]
Christine Cole
Posted by developer: Fixed as of the upcoming MySQL for Excel 1.3.7 release, and here's the changelog entry: User-selected data types that replaced the detected values of a column were lost when the First Row Contains Column Names check box was selected or deselected in preparation for an export-data operation. This fix retains the selected value when the data type is set manually to override the automatically detected type and the check box is selected or deselected. It further adds a new action to reset the column back to automatic detection. Thank you for the bug report.