Hello,
We work on large assemblies (about 700 to 900 pieces).
When a single part is checked out, it prevents the extraction of all drawings, even those that are not affected by the part that has already been extracted.
Is there a solution to force the extraction?
Thank you in advance for your feedback,
Sébastien
Hello and welcome;
Please specify the versions of the software used:
Solidworks (Version ? + local type ? or online ?)
and
PDM
Hello Maclane,
Indeed I forgot the essential.
SW 2023 SP2.1 on-premises
SW PDM 31.2 (B1) Local
Other info: I am not an administrator of the PDM.
Thank you!
Hello,
You will have to go see the EPDM admin because either it is a problem of user rights, or it is a problem of workflow.
A classic trick is to want to do the extraction via Windows Explorer while the file is opened via the assembly in Solidworks.
Even if it's annoying, this blocking is normal (as the file is opened by solidworks it is blocked to change its state via the file explorer). The solution: do the extraction via Solidworks (or close the assembly in Solidworks and do the extraction via the explorer).
Nb: as SW is not the champion of freeing files/RAM, doing the extraction via SW is often the fastest (you are not safe from having another file blocked by SW when a priori it should no longer be).
Well, I don't have PDM... but according to the help:
https://help.solidworks.com/2023/french/EnterprisePDM/FileExplorer/r_File_Check_Out_Dialog_Box.htm?id=0.3.1.0
So @froussel is right, we must approach the Administrator of PDM.
Note: it is indicated that the PDM is " local ", it is curious that the user is not the administrator in this case, right?
Hello Froussel,
I do the extraction under SW after opening the file when SW offers me to.
The behavior of the PDM is normal since I want to update a plan pointing to an assembly file from which an element is extracted (and therefore potentially being modified). So my plan is in theory impacted. Except that my plan is partial on the whole and I don't use the extracted component (I know this and SW can't know). I wanted to know if there was a way to force the ban of SW PDM in this specific case.
" Local " = " on-premise " on the company's server as opposed to " cloud " on the Dassault sys server.
I am not adm.
But my adm also doesn't know a solution.
NB: Thank you for the link to the doc, but I had already read it before addressing the forum 
It looks like it is related to version change rights → it is the PDM admin who can change the settings.
Otherwise you archive your part the time to update your overall MEP, right?
Just a little thing at the time (2017 
) the management of extraction and archiving
By going through SW or PDM, you had to recharge the part it seems to me??
According to the procedure:
- I extract the part or assembly, I open it. And when SW poses a problem, I reload
- I open my part on SW, I extract my part via SW and I load the part by unchecking read only
When there was a problem, always ask for the latest version on PDM, to be sure that you are up to date in terms of cache and other.
See below the manipulation, but you probably knew it
Hello Froussel,
Thank you for stirring your minds for my problem 
[quote=" froussel, post:8, topic:114465 "]
It looks like it is related to version change rights
[/quote] The file extracted by my colleague is indeed in SW2023.
For your information, I'm working on a subset plan. I can't archive it, since I couldn't extract it!
Hello Fred78,
For your information, I'm an old hand at Catia (26 years of experience!) but I've just been sliding to SW for 6 months. So I have very little luggage under SW.
I looked at the reload function. Indeed, I find it available on the part file extracted by my colleague, but I don't have the hand to uncheck read-only.
SCREENSHOT WHEN EXTRACTING THE PLAN
SCREENSHOT RELOAD FILE
No pot, switch from CATIA to SW 
Don't hesitate to recharge, the solution may not be there. It looks like rights as explained earlier, if you have tried everything.
Last solution if this part does not need a history, rename it after having overridden the original part. You take back control and archive it by keeping it extracted.
When opening an assembly or drawing, a message will tell you that it has the right name but it is not the original part. As it is an exact copy there will be no problem.
Another question:
Has this piece been directly in an assembly?
Tried to open the assembly that contains this checked out part and or checked it in after opening. And close the assembly. Try checking out the part again and opening it in SW
The 10000127 file is already extracted (logically by someone else). So it seems logical that you can't extract it a second time.
Nb: It must happen sometimes that a file is extracted on your computer but you can't work on it. Often Windows Read/Write problems if EPDM or the explorer crashed at the time of extraction (PDM considers it extracted but in practice it is read-only on the computer).
In this case, try to change the read-only to the mano via the right click on the file.
But normally the owner user or administrator should be able to cancel the checkout?
Unless there is a problem (of the kind I described above), normally yes: the user who checked out should be able to either archive or cancel the check out (unless they have added nuances of rights since EPDM 2020: it's not totally impossible even if it doesn't seem necessary).
Hello,
No, nothing has been added to rights for years.
For me, since there is no warning reported on the SLDDRW file (file that @Sébastien_QUÉREL trying to extract), I only see a rights problem (among other things the fact of not displaying as a warning the fact of not having the rights to extract).
I'll lean towards an SLDDRW file that isn't in the same workflow state as the SLDPRT file, which could explain why the extraction action is impossible.
I tested on 2025 the fact that the SLPDRT file is extracted does not block the extraction of the plan on another workstation.
Edit: and I don't remember this kind of bug on previous versions (2020/2021/2022/2023/2024)
1 Like
Hello @Cyril_f
In PDM, the rights are written to the folder, not to the file? Although possible, surely?
Normally if the part or assembly is attached to the plane it follows the worksflow
In my time I don't know if this is the case, the 3D did not follow the Workflow, it was just temporarily blocked during the validation of the plan. And released either by the draftsman or the CP during a new revision. The 3D was not indicated in the workflow
Are we sure?
I'll look at the ignored messages in Solidworks, you never know:
https://www.javelin-tech.com/blog/fr/2026/04/how-to-restore-solidworks-dismissed-messages/
ps: On the Javelin website I came across this article too:
This is one possible explanation...
"Windows 11 File Explorer does not update the folder path in the SOLIDWORKS PDM File Vault correctly"
https://www.javelin-tech.com/blog/fr/2024/07/troubleshooting-solidworks-pdm-windows-11-file-explorer-not-updating-correct-folder-path-in-solidworks-pdm-file-vault/
Folder rights + workflow right regardless of the type of extension.
After that, there are the warnings that can be configured by group or user