Shared Resource Set – newly added resources not offered during update in other projects

Simone Bissi

Hello,

I recently migrated several projects from StreamServe 5.6 to Exstream 16.6, which uses CAS-based versioning.

In the old environment I had a single shared resource set containing overlays, fonts, images, lookup tables, etc., referenced by all projects. During the migration import I used the "reuse resources with the same ID" option, so the shared resource set was imported only once and all 12 projects reference the very same set of resources — no duplicates.

Now I have run into the following issue:

1. Inside Project A, I opened the shared resource set and added a brand-new image resource that did not exist before.
2. I checked in the resource set and released it.
3. I then opened Project B, which references the same shared resource set.
4. I triggered an update to pull in changes from the shared resource set.
5. The update wizard correctly shows the resources that were already present at import time and asks me whether to keep the current version or download the newer one — fine.
6. However, the newly added image (which was not present in Project B at all) is never offered in the update dialog. It simply does not appear, so I have no way to pull it into Project B.

Questions:

• Is this the expected behaviour when a resource set is shared via the "same ID" import strategy?
• Is there a specific workflow to propagate new resources (not just updated ones) from a shared resource set to other projects that reference it?
• Do I need to explicitly re-import the resource set into the other projects, or is there a way to force a full reconciliation?

Any guidance or pointer to the relevant documentation would be greatly appreciated.

Thank you.

Simone Bissi

Update / Root Cause Found

After some testing I was able to identify the root cause of the issue.

When I imported the projects from StreamServe 5.6.2 into Exstream 16.6 using the "reuse resources with the same ID" option, that option worked correctly for the individual resource files inside the resource set (overlays, fonts, images, etc.) — those are indeed shared and appear as a single instance across all projects. However, it did not work for the resource set container itself: each project ended up with its own separate copy of the container, even though the contents are the same shared objects.

I confirmed this by creating a brand-new resource set from scratch, adding it manually to a second project, and then adding new resources to it: in that case the update mechanism works perfectly and new resources are correctly propagated to all projects referencing that container.

New question

Now I need to fix the existing setup without starting from scratch.

I already have one "master" resource set container that is fully populated with all the shared resources currently in use. The other projects each have their own separate container pointing to the same underlying resource files, but the containers are not the same object in CAS.

Is there a supported way to replace the resource set container in each project with the single shared master container, without having to manually re-add every individual resource one by one inside each project?

Ideally something like a "swap container" or a re-import with a forced ID remap at the container level — but I could not find anything in the documentation. Any suggestions or workarounds would be very welcome.

Thank you.