Rocket Software Homepage
Forum Home Forum Home > AccuTerm Knowledge Base (read only) > File Transfer
  New Posts New Posts RSS Feed - File upload issues
  FAQ FAQ  Forum Search   Register Register  Login Login

The AccuTerm forum has moved. Go to community.rocketsoftware.com to register for the new Rocket forum.

Forum LockedFile upload issues

 Post Reply Post Reply
Author
Message
Shrek59 View Drop Down
Senior Member
Senior Member


Joined: December 04 2006
Location: New Zealand
Status: Offline
Points: 208
Post Options Post Options   Thanks (0) Thanks(0)   Quote Shrek59 Quote  Post ReplyReply Direct Link To This Post Topic: File upload issues
    Posted: June 20 2013 at 9:59am
Hi Pete,

I've struck a couple of issues with uploading CSV data into OpenQM (v3.0-8 Windows) using AccuTerm 7.1a SP2 (7.1.1012) on Windows 7 / 64 Home Premium.

The import data uses comma separators, and has a header row that matches the dictionary names of the receiving file.

Using the file transfer wizard, everything goes fine EXCEPT that the header row is imported into the receiving file. I ticked the 'User header row' option on the way through, so I wouldn't expect this to happen.

Using FTD directly from the command line, I get the message:

Transfer status: Attribute defining item 'ROW,QUARTER,COUNTRY,DESCRIPTION,QTY,FOB' not on file

Looking through the code for FTD, this looks as the variable ALST is not set when you answer Y to the 'Use header record' prompt.

Any thoughts?

Thanks,

Brian Speirs
Back to Top
PSchellenbach View Drop Down
Admin Group
Admin Group

Moderator

Joined: December 15 2003
Location: United States
Status: Offline
Points: 2150
Post Options Post Options   Thanks (0) Thanks(0)   Quote PSchellenbach Quote  Post ReplyReply Direct Link To This Post Posted: June 21 2013 at 4:21am
Hi Brian -

I'm not sure why you are having difficulty uploading using FTD. Are you sure you have the delimiter set to 'comma' when performing the upload? The error you are getting looks like maybe you have the delimiter set to tab.

Thanks,

Pete
Back to Top
Shrek59 View Drop Down
Senior Member
Senior Member


Joined: December 04 2006
Location: New Zealand
Status: Offline
Points: 208
Post Options Post Options   Thanks (0) Thanks(0)   Quote Shrek59 Quote  Post ReplyReply Direct Link To This Post Posted: June 21 2013 at 10:30am
Hi Pete,

You were quite right. Changing the delimiter to Comma made everything work just fine - including the fact that the header row was not imported when running FTD directly.

So, that brings us back to the first issue - why is the header row being imported when the import is run via the wizard?

Thanks,

Brian
Back to Top
Shrek59 View Drop Down
Senior Member
Senior Member


Joined: December 04 2006
Location: New Zealand
Status: Offline
Points: 208
Post Options Post Options   Thanks (0) Thanks(0)   Quote Shrek59 Quote  Post ReplyReply Direct Link To This Post Posted: June 22 2013 at 4:55pm
Let's add a bit more to this - the import wizard doesn't always import the header row, but with those data sets it did so every time.

Here are the first couple of rows of the import:

ROW,QUARTER,COUNTRY,DESCRIPTION,QTY,FOB
1,20074,Afghanistan,Animals; live,..,0
2,20074, ,Meat and edible meat offal,..,0

Yes - those are two dots in the QTY field, and there is a space character in the COUNTRY field for most rows.

ROW is a standard QM dictionary item:

1: D
2: 0
3:
4: Row
5: 7R
6: S

The only things vaguely unusual here are that I am specifying attribute 0, and that it is right-justified (whereas ID fields are left-justifed by default). I can't see that any other dictionary items would have an impact on whether the row is saved into the QM file.

Maybe that will help trace the issue.

Cheers,

Brian
Back to Top
PSchellenbach View Drop Down
Admin Group
Admin Group

Moderator

Joined: December 15 2003
Location: United States
Status: Offline
Points: 2150
Post Options Post Options   Thanks (0) Thanks(0)   Quote PSchellenbach Quote  Post ReplyReply Direct Link To This Post Posted: July 30 2013 at 5:23am
Hi Brian -

This looks like a bug in the wizard. When you specify that the first line is a header, and you match dictionary names to columns, somehow the header line is treated as data. If you select "include all columns" instead, then the header line contents are matched with dictionary names and the header line is not treated as data. I'll add this to my "need to fix" list.

Thanks,

Pete
Back to Top
Shrek59 View Drop Down
Senior Member
Senior Member


Joined: December 04 2006
Location: New Zealand
Status: Offline
Points: 208
Post Options Post Options   Thanks (0) Thanks(0)   Quote Shrek59 Quote  Post ReplyReply Direct Link To This Post Posted: July 30 2013 at 9:43am
Thanks, Pete. We'll look forward to the fix.

Cheers,

Brian
Back to Top
 Post Reply Post Reply
  Share Topic   

Forum Jump Forum Permissions View Drop Down

Forum Software by Web Wiz Forums® version 12.03
Copyright ©2001-2019 Web Wiz Ltd.