While we can raise the feature request on your behalf, it would be preferable for it to be submitted through the Community Portal. This allows the engineering and product teams to review, prioritize, and provide updates on the request directly.
 
Once the feature request has been submitted, please share the link with us here.
 

Next Steps

• Submit the feature request through the Community Portal.
• Share the feature request link in this ticket.
• We will create a separate access ticket to track the feature enhancement.
• Following the initial analysis, we will be able to provide an estimated timeline for implementation.

 
Let us know if this works for you. Thank you for your cooperation.

Thanks for the question and feedback, Leo!

I did some digging, and here are a few items worth outlining and sharing:

Why Fund Hierarchy Is Special
Fund hierarchy is not just a list of Fund organizations — it's the parent-child tree structure that shows how Funds roll up into one another.

In Workday's API taxonomy, this hierarchical structure is exposed through a separate API operation: Get_Fund_Hierarchies. And critically, Workday places this operation in the Cash_Management module, not the Financial_Management module.

This is analogous to how:

• SPEND_CATEGORY_HIERARCHY(supported
• REVENUE_CATEGORY_HIERARCHY(supported
• PROJECT_HIERARCHY(supported
• FUND_HIERARCHY(not supported Cash_Management

Each hierarchy type has its own dedicated API operation, and Workday chose to place Fund hierarchy management under Cash_Management. Probably (guessing here!) because Fund management (including fund availability, bank statements, and fund structures) is a treasury/cash management function in Workday's product architecture, even though Fund is used as a worktag across Financial Management.

The ORGANIZATION_HIERARCHY_DETAIL table in the WFM connector captures hierarchy relationships for org types returned by Get_Organizations (Financial_Management module). If Workday's Get_Organizations does not return Fund as an org type (or returns it without hierarchy detail), then Fund hierarchy would be absent from ORGANIZATION_HIERARCHY_DETAIL even though other org hierarchies are present.

The Get_Fund_Hierarchies endpoint in Cash_Management is the dedicated operation for this data, and since Fivetran's WFM connector doesn't call Cash_Management APIs, this data is simply never fetched.

TL;DR Fund worktag values are a Financial Management concept. Fund hierarchy is a Cash Management concept in Workday's API taxonomy.

Fivetran's connector covers the former but not the latter because Get_Fund_Hierarchies lives in a module the connector doesn't currently call. This is a connector coverage gap, not a fundamental impossibility; adding Cash_Management module support (or just the Get_Fund_Hierarchies endpoint) would resolve the missing data issue here.