关于PLTR Foundry多语言显示数据集列名及对象类型属性名的技术问询

Hey there! Great question—let’s break down Palantir Foundry’s capabilities around multi-language support for dataset column names and Object Type properties, especially compared to SAP’s login-based auto-switching feature.

First, let’s set the baseline: Foundry’s core metadata layer (for datasets and Ontology Object Types) is built around English identifiers by default. This design choice prioritizes consistency across data pipelines, code repositories, and cross-team collaborations where standardized, machine-readable names are critical.

Now, to your key ask: Foundry does not have an out-of-the-box, native feature that automatically switches column/property names based on a user’s login language, exactly like SAP’s functionality. However, there are several practical workarounds and supported features that can achieve a similar result:

• Ontology Object Type Property Localization
  For Ontology Object Types, you can use Foundry’s display name configuration with multi-language support. In the Ontology Manager, define localized display names for each property across different languages. When a user switches their Foundry session language (via account settings), these display names will automatically render in the selected language. Note this applies only to the Ontology layer—underlying dataset column names remain as original identifiers, but mapping datasets to Ontology Objects lets users interact with localized names in most Ontology-powered experiences (like Object Explorer, Action Forms).

• Dataset-Level Localization Mapping Layer
  If you need localized names directly in dataset views (e.g., Dataset Explorer, Contour), build a lightweight translation setup:

  1. Create a reference dataset mapping original English column names to localized names, paired with language codes (e.g., en, de, fr).
  2. Use Foundry Transforms or Contour calculated columns to dynamically pull the correct localized name based on the current user’s language (fetchable via Foundry’s user context API with user.language).
  3. This requires ongoing maintenance (updating the reference dataset for new languages/columns) but offers flexibility for dataset-specific multi-language display.

• Custom Application Internationalization
  For custom Foundry applications (React-based or using Foundry’s App Framework), you have full control over multi-language rendering. Integrate an i18n library (like react-i18next), predefine translations for column/property names, and fetch the user’s login language via Foundry’s Auth API. This lets you replicate SAP’s seamless auto-switching experience exactly, though it requires front-end development effort.

One final tip: Foundry’s product team iterates based on user feedback. If this native auto-switching feature is critical for your organization, submit a feature request through Palantir’s official support channels—they prioritize requests based on user demand.

备注：内容来源于stack exchange，提问作者Lex Knape