When I try to rename a file in PDM (manually or during a transition via a mypdmtools action), the action is impossible because an assembly using this file is extracted to another computer. However, it is not the current version of the extracted assembly that uses this file, but an earlier version! So I find this blockage surprising. Have you ever encountered and successfully worked around this problem?
More generally I am very annoyed by the renaming block when an assembly is opened/extracted on another computer, the PDM system having been sold to me as allowing to manage links dynamically without worrying about file names/locations. I imagined that the renaming could be done on the server side without worrying about the client workstations, by simply indicating the new discrepancy.
To my knowledge, before the 2018 version it was possible. As of this release, it is no longer possible to rename a low-level file that would be used in an extracted n+2 level assembly (contained in a subassembly, not directly linked).
It's the same behavior when you want to undo transitions in the history (when no version has been created in between).
A bit of a regression in my opinion but probably implemented for stability reasons. Maintaining links in the event of a base rename can only be done if the direct parent is archived. Why did they go up this mechanism to all the joker levels (since you just have to reload the renamed element).
@Cyril.f thank you for your feedback. Iagree with you on the regressive side, I can at the limit understand the block if the direct parent level N+1 is extracted, but for the levels beyond that it is beyond me.