Unexpected sort results using get_data from the Eikon Python API

nick.zincone

Using version 0.1.7 of the Python Eikon API, I'm seeing some unexpected results when attempting to sort my data. Using the TR_Field function, it provides both the direction of the sort and the priority within the overall sorting expression. The documentation states the highest priority is 0 and the default is None. While there is no description of what 'None' means, I'm assuming if the field is set to None, then this field is not part of the sort algorithm.

For example,

>>> bid=tr.TR_Field('BID')
>>> bid
{'BID': {'sort_dir': 'asc'}}

Doesn't set the sort_priority. I'm assuming because it is not defined within the expression, it must be set to none. Therefore, any data I request for that asks for bid, will not attempt to sort - will display based on the order of the instruments I'm interested in.

However, when I explicitly set the priority to 0, it doesn't seem to make a difference. (See screenshot below).

When I set the priority to 1, I then see the expression include the priority which I would expect the sorting would take affect. However, based on the example within the screenshot below, the data is not ascending, but descending.

As a further test, I explicitly set the sort_dir to 'desc'. When I do this, the display sorts the data - but in ascending order.

This behavior is not expected.

tomas.kourim

I came across this problem myself. It's a bug. The following is some code within the eikon module data_grid.py that corresponds to the get_data function.

if sort_priority:field[field_name]['sort_priority'] = sort_priority

When sort_priority is set to 0, the if check evaluates to False. Thus it gets no sort_priority.