I was surprised that the security names returned by lookupSecurity() could not be passed directly to another Rblpapi function, like bdh(). I haven't looked at the code to understand where those values come from, though I suspect they're simply passed-through from whatever the API function returns.
So I'm soliciting feedback for the best way to achieve what I want. The options I can think of off the top of my head:
Modify lookupSecurity() to return security names that can be used in other functions
Add a translator function
I was also surprised that the yellowkey values were not consistent with what needs to be used when specifying a security name. Support for that could be added without changing the current defaults.
All of those would strike me as _API_ issues we cannot do much about given the famously opaque documentation. But if you can come up with workarounds, let us know.
I was surprised that the security names returned by
lookupSecurity()
could not be passed directly to another Rblpapi function, likebdh()
. I haven't looked at the code to understand where those values come from, though I suspect they're simply passed-through from whatever the API function returns.So I'm soliciting feedback for the best way to achieve what I want. The options I can think of off the top of my head:
lookupSecurity()
to return security names that can be used in other functionsI was also surprised that the
yellowkey
values were not consistent with what needs to be used when specifying a security name. Support for that could be added without changing the current defaults.