Configuration Path vs. Flat Path in Hyperlink
Hi all.
I do have a problem specifying the correct Hyperlink string for accessing the content of a member stored in SI.
We use Hyperlinks like
to add a read only reference to either a static ro floating revision in many occasions.
Imagine the path above /Playground/KM_Work/common/_global_1/project.pj . This project has two possible top level projects:
- /Playground/project.pj (with a OpenProject Permission only for Admin Users)
and
- /Playground/KM_Work/common/project.pj (with a OpenProject Permission for Developer Users as well)
In contrast to a Flat Path, the Configuration Path is able to tell the difference:
- #/Playground#KM_Work/common/_global_1/project.pj
and
- #/Playground/KM_Work/common#_global_1/project.pj
as the the part between the first two hashes ('#') defines the top level project.
Recently the situations added up, where this "Flat Path" definition of the project in the Hyperlink leads to "ambiguous project" problems, where the hyperlinks leads to a error MKS125212: The project file /Playground/project.pj is not registered as a top level project with the current server
when a Developer tries to open the Hyperlink.
This happens kind of randomly and has nothing to do with the ACL setup, as the Developer User can access the project and member via the Client GUI or the CLI without any problem.
This is a known and documented limitation of the Flat Path and I assume one of the reasons why it is deprecated and PTC encourages users to use the configuration path instead.
Knowing all this, I wanted to change my Hyperlinks so they use the configuration path instead.
Unfortunately this seams to be tricky.
In the CLI you can simply exchange the Flat Path and the configuration path but calling the web-client with
leads to MKS124808: This command requires operands: member
Any Help will be appreciated
BTW:
I'm using I10.2 but this applies for all Integrity Versions since at least 2007.