# Global branch visibility across platform

**URL:** <https://community.palantir.com/t/global-branch-visibility-across-platform/7296>\
**Category:** Product Feedback\
**Tags:** ontology-management, global-branching\
**Created:** [September 29, 2026, 9:08pm UTC](https://community.palantir.com/t/global-branch-visibility-across-platform/7296 "2026-09-29T21:08:46Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Benutzer7](https://yyz1.discourse-cdn.com/palantir/user_avatar/community.palantir.com/benutzer7/32/8327_2.png) [@Benutzer7](https://community.palantir.com/u/Benutzer7)\
**Post date:** [September 29, 2026, 9:08pm UTC](https://community.palantir.com/t/global-branch-visibility-across-platform/7296/1 "2026-09-29T21:08:46Z")

</div>

Hey all,

Ive got an opportunity to play around with global branching recently. It really is a game changer compared to before.

But there are few drawbacks that I came across(or am I missing a setting/maybe the feature is not available in my stack just yet) -

- Post transform is build in global branch, the dataset can only appears as a rawdataset in files as it is not directly possible to move around folders/files using global branch selected (I assume its “Main” by default as there is no option to make a selection)

- The global branch in Ontology Manager did not make the newly created dataset available for selection when trying to create an object type (as it was not discoverable to pick using the “use existing datasource → Select datasource” which is the usual flow to create an object type)

- Another drawback is when working in “Workshop” using the global branch; it does not automatically save changes

- + It will also neither detect an Action created in “main” or let us use it in the created “global branch”, so the only way out is duplicating the same

---

<div class="post-metadata">

**Author:** ![maxh](https://avatars.discourse-cdn.com/v4/letter/m/c77e96/32.png) [@maxh](https://community.palantir.com/u/maxh)\
**Post date:** [October 6, 2026, 10:13pm UTC](https://community.palantir.com/t/global-branch-visibility-across-platform/7296/2 "2026-10-06T22:13:48Z")

</div>

Hi, providing general guidance here based on what I could interpret from your post alone

**1. Dataset placement and the “raw dataset” label**

Global Branching does not give you a separate Compass folder tree. Moving a file is a shared resource-location change, not an isolated change on your global branch. If you’re referring to viewing a dataset version, you can select master, or view any branched versions.

See [Global Branching concepts](https://www.palantir.com/docs/foundry/global-branching/core-concepts/#editing-resources)

**2. Selecting the new dataset in Ontology Manager**  
Ontology Manager supports loading datasource schemas from the dataset branch associated with the selected global branch. Check that:

- Ontology Manager and the transform are using the **same global branch**.
- The output has a successful build and a readable schema on that branch.
- You have access to the dataset, and the picker’s search/filter settings aren’t excluding it.

Try locating the dataset by its RID or browsing directly to its folder.

**3. Workshop autosave**  
Try to save the module manually once on the selected branch. I believe autosave is disabled until an initial module version exists on that branch. Subsequent edits can be autosaved as drafts, but that is separate from explicitly saving a version. See [Branching Workshop modules](https://www.palantir.com/docs/foundry/workshop/branching-integration/).

**4. Actions created on `main`**  
If the action was created after your ontology branch diverged, try **Ontology Manager → Main branch updates → Rebase branch** rather than duplicating it. Once you modify the ontology on a branch—including indexing an object type—new changes from `main` require a manual rebase. See [Ontology rebasing](https://www.palantir.com/docs/foundry/ontologies/branching-ontology/#rebasing-and-conflict-resolution).

To execute the action on the branch, all object types it edits must also be indexed there. Action-generated object edits are for testing and are **not merged into `main`**. See [Branching action types](https://www.palantir.com/docs/foundry/action-types/branching-action-types/).