You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 31, 2021. It is now read-only.
"there are also a host of other "run-time" methods registered with the TimeScape Data Server that can also be utilised in expressions etc, which is what I am referring to below. These methods can come from any 3rd part add-in registered with the system.. These are not yet exposed to the NET API in a structured fashion.
In the meantime though, there are ways of getting to the information by executing a query as follows:
expression context.P?
This will tell you what properties (which can be attributes of data & not just stored data) are available to be used next in the query expression.
Eg. ITEM(...).PriceOfferClose.P?
Similarly, if you want to know what functions/methods are (potentially) available, you can use F? to get that list.
Eg. ITEM(..).PriceOfferClose.F?
Which might give you back a list including VOLATILITY().
From there you can get the available arguments by using U?, as follows:
ITEM(..).PriceOfferClose.VOLATILITY.U?
All of these things have to be resolved by executing queries as opposed to relying on schema, as they are determined at run time (ie. query time) as they depend on database state (not schema) to determine what properties/functions are available.
So, at present that's the only way to do it. Any consumer of the query response would need to execute the query as each dot (.) was introduced into the typed expression and then process the result to determine the list of functions/properties that should be offered in the next drop-down list."
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
From Chris B.:
"there are also a host of other "run-time" methods registered with the TimeScape Data Server that can also be utilised in expressions etc, which is what I am referring to below. These methods can come from any 3rd part add-in registered with the system.. These are not yet exposed to the NET API in a structured fashion.
In the meantime though, there are ways of getting to the information by executing a query as follows:
expression context.P?
This will tell you what properties (which can be attributes of data & not just stored data) are available to be used next in the query expression.
Eg. ITEM(...).PriceOfferClose.P?
Similarly, if you want to know what functions/methods are (potentially) available, you can use F? to get that list.
Eg. ITEM(..).PriceOfferClose.F?
Which might give you back a list including VOLATILITY().
From there you can get the available arguments by using U?, as follows:
ITEM(..).PriceOfferClose.VOLATILITY.U?
All of these things have to be resolved by executing queries as opposed to relying on schema, as they are determined at run time (ie. query time) as they depend on database state (not schema) to determine what properties/functions are available.
So, at present that's the only way to do it. Any consumer of the query response would need to execute the query as each dot (.) was introduced into the typed expression and then process the result to determine the list of functions/properties that should be offered in the next drop-down list."
The text was updated successfully, but these errors were encountered: