E2E Traceability Error: "This ressource does not exist ..." when trying to link Physical Product to CATIA Magic block in 3DEXPERIENCE

Hi everyone,

I am trying to establish a digital thread and create a link directly between a Physical Product in 3DEXPERIENCE and a Logical Component (Block) coming from CATIA Magic. Currently, the integration via Cameo DataHub to link and sync requirements with elements in CATIA Magic is working, as well as publishing system models to view in 3DPlay and importing variabilities from 3DEXPERIENCE to CATIA Magic.

My Setup & Environment:

  • Rich Client: CATIA Magic System of Systems Architect 2026x

  • Storage Mode: The project is saved and changes are committed to the 3DEXPERIENCE platform.

Plugins installed & active:

  • Cameo DataHub

  • Magic Model Analyst

  • 3DEXPERIENCE ENOVIA Model Definition Integration

  • Cameo Collaborator Publisher

  • Product Line Engineering

  • Variability Core

Project Usages:

  • DataHub Profile

  • Document View Collaborate Profile

  • MBPLE Profile

  • 3DEXPERIENCE Profile

  • 3DX TRM Profile

  • Variability Profile

  • SysML Template for Cameo Collaborator

  • (and other standard profiles)

3DEXPERIENCE Web App:

  • Systems Traceability Analyst widget

The Problem:
When I open the Systems Traceability widget in the web dashboard, I can see my Physical Product and my unpacked Magic project tree down to my block.

However, as soon as I try to create the link by drag-and-dropping the block onto my physical product, the platform prompts me with the following error:
"This resource does not exist or is in a state that does not allow to do this action."

I have tried several different ways, but I am never able to create a link between the block and the physical product.

An interesting observation:
When I compare the display of my model in the widget with videos from official webinars, mine appears in the same coloration as inside CATIA Magic. In the webinars, however, all elements from CATIA Magic are colorized in a light blue.

At the moment, I can't find what I'm missing to resolve this issue. Is this a server-side configuration, a specific mapping setting, or a license issue?

Any help, schema, or configuration hint would be greatly appreciated!

Thanks in advance,
Jannis Lützelschwab

Adel TAGHIYAR 

Answers 0