logo
Welcome Guest! To enable all features please Login or Register.

Notification

Icon
Error

Options
Go to last post Go to first unread
kddupont  
#1 Posted : Thursday, February 2, 2017 2:37:20 AM(UTC)
kddupont

Rank: Newbie

Groups: Registered, Registered Users, Subscribers
Joined: 4/28/2005(UTC)
Posts: 8
Location: Ohio

Was thanked: 1 time(s) in 1 post(s)

I just installed today's downloader update (15.0.42.57).  Now every attempt to convert CSV data fails with a "Failed yearly timestamp check"

 

Additional information.  Further testing seems to indicate that the issue takes place when attempting to convert < 3 records.  Ability to append data still not working however.

 

 

Edited by user Friday, February 3, 2017 2:58:29 AM(UTC)  | Reason: Added additional information after additional testing.

MS Support  
#2 Posted : Friday, February 3, 2017 3:30:37 PM(UTC)
MS Support

Rank: Advanced Member

Groups: Moderators, Registered, Registered Users, Subscribers
Joined: 10/8/2010(UTC)
Posts: 1,631

Thanks: 52 times
Was thanked: 130 time(s) in 126 post(s)
Hi, Can you Copy/Paste the CSV data into a post? If it is failing validation it will fail to append, so we really need to determine why it is failing the data validation first.
kddupont  
#3 Posted : Saturday, February 4, 2017 6:11:38 PM(UTC)
kddupont

Rank: Newbie

Groups: Registered, Registered Users, Subscribers
Joined: 4/28/2005(UTC)
Posts: 8
Location: Ohio

Was thanked: 1 time(s) in 1 post(s)

Hi,

Here is the data...

<date>,<open>,<high>,<low>,<volume>,<close>
2/1/2017,48.93,49.810001,48.68,22446,49.259998
2/2/2017,48.880001,49.00,48.470001,13522,48.900002

 

Please note the following:  I only receive the timestamp error message when attempting to convert <3 records. 

As an FYE, the failure to append has been present for a while (any updates overwrite all data ...even when overwrite checkbox is not checked.

Thanks.

 

 

 

MS Support  
#4 Posted : Saturday, February 4, 2017 7:45:14 PM(UTC)
MS Support

Rank: Advanced Member

Groups: Moderators, Registered, Registered Users, Subscribers
Joined: 10/8/2010(UTC)
Posts: 1,631

Thanks: 52 times
Was thanked: 130 time(s) in 126 post(s)
Hi, There is a minimum amount of data needed to automatically determine the periodicity. I believe it is around 3-4 records. In the event you are converting less than this, you will need a Periodicity Column (which also requires a Ticker column). If the data is formatted as follows (I just used IBM as an example symbol) the data should successfully convert. The conversion report had a bug previously where it was displaying the Source data in the report. This has now been changed to reflect the Destination security file. Keep in mind you will be viewing the entire security file in the report, not just what was converted. <date>,<ticker>,<per>,<open>,<high>,<low>,<volume>,<close> 2/1/2017,IBM,D,48.93,49.810001,48.68,22446,49.259998 2/2/2017,IBM,D,48.880001,49.00,48.470001,13522,48.900002
MS Support  
#5 Posted : Saturday, February 4, 2017 7:48:16 PM(UTC)
MS Support

Rank: Advanced Member

Groups: Moderators, Registered, Registered Users, Subscribers
Joined: 10/8/2010(UTC)
Posts: 1,631

Thanks: 52 times
Was thanked: 130 time(s) in 126 post(s)
Also, the fact that the file is showing up as Yearly is likely a bug. It should likely not display at all but there may be a limit to how much we can filter out when the file is not formatted quite right. I will write the issue up either way to look at.
kddupont  
#6 Posted : Saturday, February 4, 2017 9:54:22 PM(UTC)
kddupont

Rank: Newbie

Groups: Registered, Registered Users, Subscribers
Joined: 4/28/2005(UTC)
Posts: 8
Location: Ohio

Was thanked: 1 time(s) in 1 post(s)

Many thanks for the suggested change for adding a periodicity entry.  I will give that a try.

Are there any estimates as to when the failing to append issue will be addressed?  It appears that it did not make the latest update.

Thanks again!

 

 

 

MS Support  
#7 Posted : Monday, February 6, 2017 3:27:14 PM(UTC)
MS Support

Rank: Advanced Member

Groups: Moderators, Registered, Registered Users, Subscribers
Joined: 10/8/2010(UTC)
Posts: 1,631

Thanks: 52 times
Was thanked: 130 time(s) in 126 post(s)
Hi, Thank you for reporting this. I believe we were not looking at the problem in quite the right way previously, seeing it as a failure to append issue. It actually appears to replace the file entirely. We will need to look into fixing this for our next maintenance release. Unfortunately this may not be for a little bit. In the meantime, may I ask why you want to convert the data into MSLocal instead of just using it in the CSV format? (Just wondering if we can work around this issue for you in the meantime).
kddupont  
#8 Posted : Thursday, February 9, 2017 12:08:27 AM(UTC)
kddupont

Rank: Newbie

Groups: Registered, Registered Users, Subscribers
Joined: 4/28/2005(UTC)
Posts: 8
Location: Ohio

Was thanked: 1 time(s) in 1 post(s)
Thank you for the response! Needless to say, I am looking forward to the maintenance release that resolves the ability to append and not replace the entire file As to CSV vs. MSLocal.....I am looking to take advantage of the speed and other aspects of the MSLocal format.
thanks 1 user thanked kddupont for this useful post.
MS Support on 2/9/2017(UTC)
kddupont  
#9 Posted : Saturday, May 6, 2017 8:40:23 PM(UTC)
kddupont

Rank: Newbie

Groups: Registered, Registered Users, Subscribers
Joined: 4/28/2005(UTC)
Posts: 8
Location: Ohio

Was thanked: 1 time(s) in 1 post(s)

Just downloaded the latest product update (dated 5/3/2017).

Very happy to report that the data conversion issues have been resolved! 

Many thanks for addressing this bug!!

Users browsing this topic
Forum Jump  
You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.