I need to understand whether these challenges are isolated to metadata queries or represent broader

Norland

 I need to understand whether these challenges are isolated to metadata queries or represent broader platform limitations for automated portfolio analysis tools.

What I Need:

Option 1: A field that differentiates instrument type (not just class):

• Is there TR.InstrumentType, TR.SecurityType, or similar that returns: "Common Stock", "ETF", "Mutual Fund", "Corporate Bond", etc.?

Option 2: A programmatic approach that doesn't require knowing type in advance:

• Can I query all fields and use null patterns to infer type?
• Is there a universal field set that works across all instruments?

Option 3: Confirmation that this use case is not supported:

• If Workspace is not designed for automated, type-agnostic portfolio processing, please tell me directly.

Context:

During the sales evaluation process, I was assured Workspace could support my requirements and use cases, which was a basis for my subscription decision. Your team's statement that Workspace is "not fully designed for zero manual intervention" is concerning, as this directly contradicts what was represented during the sales process.

I'm not asking for custom development - I'm asking if the platform can support the use case I was sold.

Next Steps:

I need a definitive answer on the following, as soon as possible:

1. Does a field exist to programmatically differentiate Stock/ETF/Mutual Fund/Bond?
2. If not, is there an alternative programmatic approach that works?
3. If neither exists, can you confirm this use case is not currently supported?

**************************************************

We can confirm that this is not available on Workspace , since the client is using API

Is it possible to create a syntax on API similar to IF function where data items can be used whenever available for a specific instrument but we're not trained enough on API to do it

Jirapongse

@Norland

Thank you for reaching out to us.

1. I found the TR.InstrumentType field. However, this is a content question. Please contact the content support team directly for the fields (TR.xxx) that can provide the required data
   
2. The client can use the Data Item Brower tool to search for fields and parameters. As far as I know, we don't have a way to query all TR.xxx fields. Another method that can provide this information is the Search API. You can get a list of available search fields from the Search endpoint. For more information, please refer to the Building Search into your Application Workflow article.

I recommend involving the client's account team or sales representatives in this discussion.