We are having an issue with an OSDK application backed by Pilot App. Pilot App claims some of our object types are outdated. Creating a global branch in Pilot app generates an error:
An error (OntologyMetadata:DeprecatedPropertySecurityGroupsFieldUsed) occurred with this request (error id: 92dbeb26-628c-4b94-a432-acd6a1c22894).
We noticed this issue since we configured a property security policy on one our objects (Employee), which makes sense given the error.
Our policy was very simple and complied with the restrictions. We’ve since removed the policy to see if this fixes the issue, but it doesn’t.
This is not blocking us - we can create global branches elsewhere in Foundry, and in Code Workspaces we can tag and release our app. It just feels like a specific issue with Pilot App.
Hey, Chris! Good repro details, here’s what’s happening.
Root cause:DeprecatedPropertySecurityGroupsFieldUsed refers to a deprecated internal field (securityGroups) written into the ontology metadata for Employee and Position when the property security policy was first applied. Removing the policy via the UI doesn’t clean up that internal field, the stale representation persists on main.
Why only Pilot: Pilot’s branch creation runs a stricter metadata validation pass than other Global Branching entry points (Ontology Manager, Code Workspaces), which is why those still work fine.
Things to try first:
Open Employee and Position in Ontology Manager → Security tab — confirm no residual policy config is visible.
Make a no-op save on each affected object type on a branch (e.g. edit and revert the description), then merge. This can force a metadata rewrite that clears the deprecated field.
If that doesn’t work: This needs Palantir Support, the field has to be cleared directly in the ontology store. Open a ticket with:
Error ID: 92dbeb26-628c-4b94-a432-acd6a1c22894
Affected objects: Employee, Position
Context: policy applied then removed via UI, error persists in Pilot only
Felipe Montes
Development Advisor
Follow me @ linkedin.com/in/felipemontesl/ or GitHub: Brazillianerd
Hi Chris, thanks for flagging. This looks like a bug in the Pilot modification logic where we are still passing in the deprecated propertySecurityGroup field. Working on a fix to correct the issue shortly.
In the immediate term, you should only hit this issue if you make changes to ontology entities in Pilot. If you ask Pilot to revert any changes it made, then validate that is the case in the Ontology Graph / Deploy view, that will allow you to make application changes without seeing the outdated error. You can also disable Pilot from making ontology edits using the Ontology permissions dialog (click the ontology permissions button in the Ontology graph) if you would prefer to make ontology edits outside Pilot.
