I use the " Integration " utility to populate custom properties from the file name. The problem is that I can't add some files (for the vast majority, it works). The files that are problematic here are .sldprt files. When I try to add the affected files (by drag and drop or via the " add one or more documents " icon) I get the following message: " One or more documents chosen do not match the filter!"
In the Filter menu, which allows you to select the different options, all possible types of documents to be processed are checked and all possible filters are unchecked; Logically, the files concerned should therefore pass the filter.
I did some tests, by modifying the filters, by saving my file under another (shorter) name, I checked that the file is not read-only... Now I'm running out of ideas.
Have you ever encountered this problem and do you have a solution? Thanks in advance
We would need the version of the tools used to get a more precise idea: => Solidworks version => MyCadTools Version => Windows version => Solidworks local or 3DExperience?
Do you work locally or on a server?
Only some *.sldprt are problematic? In this case it is unlikely that it comes from the filters of Embedding, I would lean more towards protected locations, or special characters in the names of your files. It would be nice to have an overview of the names of the files that don't pass (and their location if possible.)
For the file names concerned, we have, for example: EP-1034201055-108-PASSERELLE K 6P NIV+12150 - CAGE LADDER ON THE SIDE OF FILE 5 I tested a copy of this file by shortening the name and removing the " + ", it doesn't work. Most other files that work follow this form and have a similar number of characters.
As for the locations, I work locally and all the files (including those that work) are in the same folder.
I had a few similar issues with the 2024sp0.0 version of the Mycad tools: Some options were unchecked, but they remained active: => Solution: We have moved to version 2025sp0.0 of the MYcad.
On the other hand, the file name is technically much too long, some restrictions on the number of characters allowed are still valid depending on the software used: for file names + their location (max 255 character limits - all included-)
A blow to get a cramp in the finger with long names like that. The file opens manually (not corrupted?) And otherwise yes the 2024 Sp0 was a bit catastrophic (for us 2024-SP2.1 because I didn't test the 2025)
Ok, I'll find out about a switch to the 2025 version. For full names, in principle, we avoid stacking subfolders; For the file names themselves, between the imposed formalism and the need to be a minimum explicit, it's not always easy to have short names
