Hi, Folks:
In the fixes for patch 20, the following bug fix reversion is listed.
SW00251512 -- User tool reports from our server have bad text wrap
characters in CSV file format. (Reverted the fix for #226412 ("\n"
cannot be recognized with Import Tool) from import tool which caused bad
text wrap characters in CSV file format.)
When I look up 226412, it has all of the related bugs that I've been
reporting about the 6.3 P19 import Tool. Since, I was previously told
that the broken code that was put into Patch 18 and Patch 19 was
considered to be a fix, I had lost all hope of ever having an Import
Tool that could:
1. Import a CSV file with large text cells that might include returns
(this has nothing to do with Excel)
2. Import a CSV file and successfully use "Define Fallback Mapping" on
core fields.
I've called Tech Support again to ask if the fix included in patch 20
was related. It has finally been acknowledged after MONTHS, that this
these import issues are indeed a defect! Item 2 directly above, was the
original issue reported on 6.3 P12 back on May 1, 2006. That was fixed
in a limited release patch 17. Defect Number 1 was introduced with P18
and P19.
The Best News is that this is FINALLY going to be fixed!
Here are more defects related to this issue:
SW00252110 Import Tool 6.3patch18 fails to recognize carriage returns as
part of the record data. Works with Import Tool 6.3patch16
SW00256959 ARIMPORT: 6.3 P19 Cannot import a .CSV with carriage
returns successfully
Michelle
A much happier camper.
_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the
Answers Are"
