News & Intel
LiveDaily AI-curated intelligence on Palantir Foundry, Ontology, AIP, Apollo, contracts, and community feedback. Updated automatically via GitHub Actions every day at 7 AM UTC.
foundry-dev-tools 2.1.24
Seamlessly run your Palantir Foundry Repository transforms code on your local machine.
Tired of struggling with Foundry alone? I built something for you
How many times have you gotten stuck with Palantir Foundry and couldn’t find a clear, well-explained resource? That happened to me too — so I decided to build Datum It’s a YouTube channel where I share Palantir Foundry tutorials from scratch, guides to earn official certifications, and everything I pick up along the way. The idea is simple: no one should have to figure out Foundry alone. Foundry fundamentals explained step by step Palantir certification prep Resources and tips that actually save you time If this sounds useful, come check out the channel and let me know what topics you’d like to see next. Building this alongside the community makes way more sense than doing it solo. https://www.youtube.com/ @datum.official See you there! 1 post - 1 participant Read full topic
Resource Managment fails to attribute usage to resources, while the data sits there in Dataset API
Resource Management is a great app to see usage, but this may be a bug. I see these false claims in the Resource Management app: “Some usage cannot be attributed to individual resources”; “Top resources” However, in the Dataset UI I can see one particular dataset which has the exact same usage perfectly attributed to it : This makes this dataset the topmost resource user! Clearly, since this data is within the system, it should be reflected in the Resource Management app too. 1 post - 1 participant Read full topic
Materialized dataset __is_deleted not behaving correctly when deleting objects through workshop
We have an object type with edits enabled, backed by a materialized dataset. The dataset schema includes the system columns _is_deleted and __patch_offset. When we delete an object via a Delete action, the row disappears entirely from the materialized dataset. We expected it to stay with __is_deleted = true so we could use it for auditing and filtering in downstream transforms. Looking at the schema, we found that the primary key resolution includes “deletionColumn”: “_is_deleted”, which appears to auto-filter deleted rows at read time. We tried removing the deletionColumn setting from the schema, but it gets set to null instead of being fully removed. After that, deleted rows did show up in the dataset, but all columns other than the primary key had null values. Additionally, the setting reverts back to __is_deleted as soon as we trigger any edit from the Workshop table that refreshes the materialized view, so the change doesn’t persist. 1 post - 1 participant
Resources: Resource Import panel requires a repository upgrade but repository is up to date
Hello Everyone, I’m trying to build a Python script to import an embedding model and the Resource Import panel claims my essentially brand new code repository is out of date. Paradoxically, when I try to update the code repository, the online VS Code environment, the local VS Code plugin, and the normal code repository interface claim the branch is up to date. Investigating further, this seems to be an issue across all the Python code repositories creation options that I currently have in my foundry; whenever I try and create a new one, I get the same issue across all the various VS Code extensions. Any advice would be much appreciated. 1 post - 1 participant Read full topic
Feature: Branching Support for Foundry Rules Engine / Rules Widgets
As far as I am aware there is no clean way to test rule changes without affecting downstream datasets as the workshop widgets don’t support branching. I understand I can use the rule preview widget to “faux-test” but you push it downstream without building the dataset. It would be nice to have branching support for these widgets/app 1 post - 1 participant Read full topic
Automation debugging and understanding behavior
Hello Community, I have an automation setup and have a few doubts regarding failure handling and debugging. Scenario My automation takes in an object set, applies a filter, and then the filtered objects trigger the automation. The automation then runs a function to update another object set. For example: Object Set A contains a large list of drivers across multiple regions along with their license numbers. Since the dataset is very large, I created multiple automations, each filtering drivers for a smaller region. These filtered objects trigger a function that updates Object Set B, where driver details and license numbers (as foreign key) need to be populated. Doubt 1: Behavior when automation fails Suppose the automation is triggered by 100 objects. The function processes the first 70 objects successfully. At the 71st object, there is an issue (for example, a validation condition causes the loop to get stuck and the function eventually
Mounting multiples files for docker container
Greetings, I’m deploying model objective via docker images. Dockerfile is like this FROM <MODEL_BASE_IMG> USER root WORKDIR /models RUN getent group 1000 ... COPY /folder/model_checkpoint /models/checkpoint RUN chown -R 1000:1000 /models USER 1000 EXPOSE 8080 ENTRYPOINT [...] CMD ["/models/checkpoint", \ "--host", "0.0.0.0", \ "--port", "8080", \ ] Each time I update the model with new model_checkpoint file, I have to build the image again while there’s no change in the environment set up. It’s quite time-wasting when the model_checkpoint file is GBs large. Is there any way I separate the model_checkpoint file and the Docker image? Like storing model_checkpoint file in some dataset, and when doing the docker run, it gets the latest model_checkpoint file from that dataset to run, then I don’t have to build the image again. Thanks in advance. 1 post - 1 participant Read full topic
Expose AIP-Analysis Functionality in OSDK
Hello, AIP-Analyst works surprising well & finding that users respond very well to the analysis it can generate. I’m noticing more users asking for custom workflows on top of AIP-Analyst (more curated front-ends, more restricted set of objects types it is able to work with, etc.). While the workshop AIP-Analyst widget works great within workshop, we are seeing more requests for this type of functionality with OSDK applications. Some specific things I’d be trying to accomplish: Pre-aggregate some object data (according to the businesses logic) to pass into AIP Analyst Custom configs (units and/or colors) for any graphs/charts it generates Specific language / verbiage the output should be using when communicating. I’m sure a lot of this can be configured with a detailed prompt into vanilla AIP-Analyst, but it would be nice to preconfigure this for the user such that burden isn’t on them to get the analysis they want. Thanks! 3 posts - 3 participants
Building agentically with AIP
Hey! It’s been a few months since I last used Foundry, and I’m noticing lots more tools available. Like new generations of AIFDE, Pilot, improved MCP, etc. I’m wondering if there is a single point of reference about how they all link together so we can best make use of them. I’m particularly interested in agentic workflows working symbiotically with agents such as Claude Code // Codex. Moreover, what is Pilot and how should we think about it vs AI FDE and productisation? Thanks! 1 post - 1 participant Read full topic
How can I enable Drop Zones in Workshop?
Hi there, The Workshop doc mentions the use of drop zones here: https://www.palantir.com/docs/foundry/workshop/drag-and-drop#workshop-drop-zones and in particular, it tells you that if it is not enabled, you should reach out to the platform admin (which is myself). I’ve been looking around in control panel to enable this feature, but so far no luck. AIP tells me the following: As an admin, Drop Handling in Workshop is typically enabled per section by toggling the “Drop Handling” option in the section configuration panel. If you or your users do not see this toggle, it may be due to a platform-level restriction or feature flag that is not exposed in the standard admin UI. In this case, you should contact your Palantir support representative to request that Drop Handling be enabled platform-wide for your environment . There is no documented setting in the Control Panel or Workshop admin tabs to enable this feature globally for all users Is this actually a platform wide config th
Inside FDP – part 3: The data architecture that makes it work
An in-depth look at the specific features of Palantir's Foundry, the commercial software platform on which FDP is built, and how the system makes use of them
Please add Color Coding for Agents / Pipeline Builder
AI - FDE currently can’t color code elements in Pipeline Builder. See screenshot. Please improve that. 2 posts - 2 participants Read full topic
About the Show & Tell category
Welcome to the Show & Tell category. We’ve created this area for members of the community to share projects, guides, tutorials etc. that solve a business or technical problem using Foundry & AIP, and discuss what they’ve built with other members of the community. We’ll hold a high bar for posting here. For example, if you are simply trying to advertise your product without concrete examples in Foundry/AIP, our moderation team will likely remove your post. Posts which feature product demo videos and/or detailed walk throughs with screenshots are what we’re hoping folks will lead with. We can’t wait to see what you’re building! 1 post - 1 participant Read full topic
Spatiotemporal resilience for Ontology: secure digital trail of regulated critical operations
Palantir’s Ontology maps real-world operations to digital objects, providing the foundation for AIP automations. However, when ingesting field data – such as a technician executing a maintenance Action or a logistics provider logging a drop-off – relying on standard GPS or static QR codes compromises data provenance. These standard inputs can be easily spoofed or manipulated, causing downstream workflows to operate on false premises. Verifying actual physical presence at a specific time remains a persistent vulnerability. The IAT4D platform solves this by anchoring physical sites with passive NFC identity chips (iMarks). When a field operator taps the iMark with a mobile device, the chip signs an external one-time challenge. OSDK-built application sends the signed checkpoints to the Foundry, where signatures are verified and ontology is updated. In this tutorial I provide samples, TypeScript v2 code, and video demonstrating one full integration that builds an identity grid, verif
Feature: State Saving for Workshop Pivot Tables
Ask: Expose row groupings & aggregations as workshop variables, so that state can be saved. Sample scenario: FDE builds a rich pivot table, with multiple complex aggregation Some row groupings are set to expandable/hidden to allow for both high-level summary & low level drilldown Some aggregations are also set to hidden User agrees to the defaults shown & hidden PAIN : Power users want to create saved views with a custom setting for row groupings & aggregations. They have multiple views, and also want to share them with other users. This is not possible, instead they need to start from the defaults and adjust them each time. 1 post - 1 participant Read full topic
TRD 100: South Florida’s resi power players usher in wealth migration
South Florida’s top residential players aren’t merely in the business of buying and selling homes. A generational wealth migration is transforming the region, and real estate’s residential business leaders are rolling out the welcome mat while navigating a c…
Global Branching Limitation with TypeScript v2 Functions
We’re trying to use Global Branching to make an end-to-end change across Ontology, Functions, and Workshop , but we’re hitting a limitation with TypeScript v2 functions . Scenario We add a new property in the Ontology within a branch We can successfully use it in pipelines and Workshop in that branch Issue Our functions are built using TypeScript v2 , and: We can’t edit or version function code within the branch The function compiler only sees the main schema So we can’t reference the new property added in the branch Impact This breaks the end-to-end workflow: Ontology, pipelines, and Workshop are branch-aware TypeScript v2 functions behave as versioned artifacts Questions What’s the recommended approach to handle this? Are there best practices for coordinating ontology changes with v2 functions? Are there plans to make TypeScript v2 repos compatible with Global Branching