| Author |
 Topic  |
|
|
Ceramicus
Germany
4 Posts |
 Posted - 07/31/2018 : 12:33:03 PM
|
Origin Ver. 2018b 64Bit
Operating System: Windows 10 (1607)
Hi folks,
I created and saved an import filter which simply says: 0 header lines (meaning, it imports the header directly into the workbook cells, which is what I want) and have a fixed number of columns (15 in this case), because only the first 4 columns are recognized when not specifically stated. I have to do it this way because the header is weird and can consist of variable amounts of lines.
This all works perfectly well when I use the Importwizard but when i apply the same import filter in batch processing, it only imports the first 4 columns. So the fixed column part in the filter seems to be ignored in batch processing and I wanted to ask if this is a bug or someone knows a solution for this.
The |
|
|
yuki_wu
896 Posts |
Posted - 08/01/2018 : 01:32:19 AM
|
Hi,
Not sure if you check the Use Import Setting in Workbook option in the batach processing dialog, which will cause the import filter disabled. Would you mind double-checking? If the checkbox is checked, uncheck it.
Regards,
Yuki
OriginLab
|
 |
|
|
Ceramicus
Germany
4 Posts |
Posted - 08/01/2018 : 06:13:21 AM
|
Hi yuki_wu,
thanks for your reply.
Unfortunately, it already was unchecked.
It directly asks me which filter to use. The fileheader gets imported into the cells, like I intend it to do, but the "number of columns" in the "Data Columns" section of the import filter gets ignored. In Batch processing, it seems to use the auto column recognition like when I dont specify the number. |
|
|
|
Ceramicus
Germany
4 Posts |
Posted - 08/01/2018 : 07:42:48 AM
|
Ok, just tested the older non-b version of Origin 2018.
There it works, so it seems to be a bug in 2018b |
|
|
|
yuki_wu
896 Posts |
Posted - 08/01/2018 : 10:44:48 PM
|
Hi Ceramicus,
Thank you for your detailed information. We could reproduce this issue now.
Yes, this is a bug in Origin 2018b and we have added this issue in our bug tracking database (ID: 18744), and this bug is targeted to be fixed in our next version.
Sorry for the inconvenience.
Thanks,
Yuki
OriginLab
|
Edited by - yuki_wu on 08/01/2018 10:46:29 PM |
|
|
|
Ceramicus
Germany
4 Posts |
Posted - 08/02/2018 : 11:40:13 AM
|
I found a work-around for my problem.
Instead of batch processing, I used the "Multiple ASCII..." import option. Here the import filter works again. And I can apply a script for which I originally wanted to use the batch processing option. |
|
|
| |
Topic |
|
Importfilter issue in Batch processing