I encountered the following error while saving changes to a logic rule in the Ontology Manager App:
‘Failed to save changes to the ontology. Inconsistent Ontology modification. A rule set binding does not have the same value reference id as the referenced rule set. This indicates a product bug, to get help, please reach out to Palantir support with the information below. ruleSetIdentifier: {“type”:“existingRuleSetRid”,“existingRuleSetRid”:“ri.ontology.main.rule-set.0d15d6fd-bad5-4e63-95e2-a57b93a87b05”} propertyTypeId: day_51 bindingValueReferenceIds: [“6ad42177-5ac5-449e-bf73-fc8f36652fd0”,“6f48bda3-083d-495b-a338-782c1c8279a0”] objectTypeId: wbg6ebf7.hcih-mrp-mvp-3 ruleSetValueReferenceIds: [“6f48bda3-083d-495b-b562-1b08a0b750e5”]’.
The error message suggests this is a product bug. I have tried refreshing and reverting changes, but the error persists. What steps should I take to resolve this, and is there a workaround or fix available?
Hello! When you say a logic rule, I assume you mean a logic rule in the conditional display formatting?
This can happen sometimes. One option is to create a new branch for your object type ‘wbg6ebf7.hcih-mrp-mvp-3’, delete the previous ruleset, create a new ruleset that you are happy with, and then merging the branch. In the meantime I will file an internal bug for this specific error so we can understand what went wrong when editing the ruleset.
Thanks for the help, I ended up resolving this by creating a foundry branch (since my ontology was creating via pipeline builder) from the current state of main branch → Rebuilding the object set (it worked this time because fresh branching apparently got rid of stale data during the previous indexing attempt) → and without any changes merging back into main.
I don’t know if this helps but from what i understand:
The mistake I made was branching out from main when indexing for some object sets were in a failed state. I then tried to make changes to main while my development branch was stuck in an endless indexing attempt. Then I tried to rectify the indexing on the main followed by a rebasing of the development branch however, this is when the error began to pop up.
Now your diagnosis of the error is precise but why removing conditional formatting rules proved futile for me was because the debugger has pointed out to a stale reference and even removing the property which references this would not get rid of the stale reference, let alone removing formatting rules. What i mean to say is if i removed all but just the primary key, it would still continue with the reference error on a property that no longer exists.
Branch out → Make no Changes → Rebuild → Merge. This mantra seems like the three finger salute for the ontology manager
1 Like
Ah I see, yeah I didn’t realise you were using pipeline builder to manage this.
We are planning some improvements to this whole workflow in the next couple of months that should hopefully stamp out these kind of out of sync errors.