[en] TS002411887 — Bad data in import causes import to never complete
[en] Fixed: Resolved an issue where, when importing from a .csv file which contains bad data, such as a '-' character in a numeric column or a number in a date column, the import "stops responding" at 99% when importing it into a table.
[en] Reproduction Steps
[en] 1. Log in to the admin client.
[en] 2. In Admin, add a calendar.
[en] 3. Lock a period in the calendar.
[en] 4. In Composer, add a table.
[en] a. From the Table type drop-down list, select Data.
[en] b. Add a Date column.
[en] 5. Import data from a text file that contains bad data (for example, a number in a Date column) into the data table.
[en] The result is the import does not complete because it gets "stuck" when trying to process the bad data in the text file.