+1 888 340 6572 GET STARTED
MultiCharts Project Management
previous_open_issue.png
Go to the previous open issue
previous_issue.png
Go to the previous issue (open or closed)
star_faded.png
Please log in to bookmark issues
feature_request_small.png
Open Feature request MC-92

QuoteManager - import from a CSV file no access to correct column

action_vote_minus_faded.png
3
Votes
action_vote_plus_faded.png
next_issue.png
Go to the next issue (open or closed)
next_open_issue.png
Go to the next open issue
Description

When importing tick data from Dukascopy, I get a file with the following format:
Date,Time,Ask,Bid,AskVolume,BidVolume
In order to import the Bid and BidVolume data, I would need the ability to access columns in the file which are not displayed in QuoteManager, as QuoteManager limit the number of columns to 5 when importing tick data. Increasing the limit to 6 columns would get round this, knowing that only 4 fields are to be imported at once.

Steps to reproduce this issue

In QuoteManager -> import data -> set Resolution to Tick, Field to Ask and count the number of columns left.

Comments (1)
#0
user-offline.png  MultiCharts Support (MultiCharts)
Feb 04, 2012 - 13:46

As a workaround you can import trades/asks/bids from 3 seprate files or 3 times from 1 file by selecting corresponding columns.

History
Issue basics
  • Type of issue
    Feature request
  • Category
    Usability
  • Targeted for
    Not determined
  • Status
    Under Review
User pain
  • Type of bug
    Not triaged
  • Likelihood
    Not triaged
  • Effect
    Not triaged
Affected by this issue (3)
People involved
  • Posted by
    user-offline.png  tcat (tcat)
  • Owned by
    Not owned by anyone
  • Assigned to
    Not assigned to anyone
  • Subscribers
    1 subscriber(s)
    Click here to show the list of subscribers
Times and dates
  • Posted at
  • Last updated
Issue details
  • Resolution
    Not determined
  • Severity
    Normal
Attachments (0)
There is nothing attached to this issue
Commits (0)
There are no code checkins for this issue
Duplicate issues (0)
This issue does not have any duplicates