Hello;
Votes and enhancement requests for Solidworks 2026 (Online or desktop) are open:
=> Vote for an improvement request with a " Like " 
=> Create your own application.
On paper, the 10 most popular requests will be taken into account by Dassault.
How I got burned on the ad this year! 
Bad luck!
But you've spent a lot of time asking for improvements, while I'm just " thumbing up" 
... It's faster. 
It's better [quote=" Maclane, post:3, topic:113124 "]
Thumb up [/quote] with the bullet up than in other assemblies or it's the thumbs down 
The most complicated thing in all this is to remember these identifiers to go vote xd
What if we started by asking for corrections before improvements. I say this because improvements will probably bring more bugs than features.
It's clear, especially since it doesn't make you want to see their " 3dswym " forum...
=> I " Poucenbalorise " 
@coin37coin , this is Dassault's solution:
1- You make the forum much less pleasant and more accessible without logging in, even in read-only mode.
2-Once you have almost no forumers left, you say that your software improves because there are fewer request tickets or other on the forum!
I'll stop there, because if I continue like this I'll change jobs and end up in front of an assembly to make a vote of confidence!
Be careful, it doesn't seem like a winning life project
@coin37coin terms of job security, that's for sure!
But in terms of remuneration on the other hand!
Edit: Whatever after looking at about 14000€/month
for barely 100€ more monthly than my current salary, indeed it's not worth it! 
No, of course not, I'm not the only one 
But I don't know how he manages at Dassault: there's the SolidWorks Enhancement Ideas Community in which you can continuously submit ideas for improvement/evolution. And then there's the TopTen list open for a few weeks (this year it's 6 months !??) in anticipation of their big mass at the beginning of February in Houston, Texas 
, the famous 3DExperience World.
I stopped posting ideas in the SolidWorks Enhancement Ideas Community; I save my ideas in an excel, and I balance everything in the TTL.
Hello team,
Indeed, like every year, they improve the MEP, but every year it's worse...
So on that note, I would say " really improve the treatment of MEP!! ", because it is much too long to open, close, register, etc. …
Uh!!! Maybe it's too much to ask... !!
@+.
AR.
Hello... 
I just came back from the shrink to whom I told my frustration about the TTL2026...
He told me:
I'd like to help you, but I don't understand anything about this list of Solid things and... Oh! Our session ends here. That's 120€ please.
So, I come to unpack my feelings on the forum...
When the TTL2026 opened up, I was super excited 
to post an idea for the drawings that for me was the best idea I've ever had...
No, but really it's not useful to read this part...
[the best idea I've ever had...] just after suggesting to a friend who was a little drunk to ski down the spiral stairs of his building... which turned out to be a very bad idea... So this idea for the TTL2026 is really the best I've had... I think.
(By the way, my friend is fine, the doctor said he has signs of brain activity again)
#JePlaisanteEvidemment
It was one of the very first I posted and yet, no one seems to have any interest in Configurations and Display States applied to drawings :
The idea is to transfer the Configuration and Display States features available for parts and assemblies to drawings; the configuration would then be renamed Composition (which would be more appropriate in my opinion).
A composition (configuration) would record the deleted/undeleted status of each sheet (another function to be added). A deleted sheet would be excluded from the number of sheets - the sheet number would be replaced by */[number of sheets] - and excluded when exporting the drawing.
Display states would maintain the same function by saving the different combinations of layer options (visibility, print), shown/hidden status, and view display style.
The goal: to manage multiple types of plans with the same drawing file. Like what:
Ideally, rather than allowing the setting of BOM options, the Composition PropertyManager would allow you to define the export options by choosing the export format and naming convention of the exported file.
Obviously, this new feature would be supported by the "Save as PDF" command: rather than asking users to select which sheets to export, they would be prompted to select the publication (configuration) to export, with perhaps the option to choose whether a selection of multiple publications results in multiple PDF documents (the default option, in my opinion) or a single document.
What do you think? Is this idea so bad?
Well, the idea seems interesting at first glance, but I wonder if it's not too specific in the sense that:
For the Notions of translations (Even if I understood that translation is only a result of the possible use of display states, sorry: " Compositions " among many others:
The vast majority of Americans are not aware that languages other than " their " English exist, let alone their non-metric system... (Measure in inches and feet... What a funny idea!) So I'm not very surprised by their lack of interest.
Most cartoonists, non-English speakers by birth, (including me) are not always inclined to do the translation of their notices or commercial plans themselves (there are always some discrepancies between translations, interpretations, the lexical richness or non-lexical of the target language (English Vs American to speak only of these languages).
=> Let's leave the job of the salespeople to the salespeople (ours will manage themselves with their low technical level (Everything is only Plate, Braket, washer and bott in their universe).
So I don't think it's the use of Composition that should be highlighted.
On the other hand, and this is why I gave my " As ". Excuse me! (another translation problem), my " like " (well I have Poucenlairizé what) your proposal is for the side of Registration and management of the Nomenclatures of the sheets according to their Composition:
The fact that you can choose the type of BOM and the destination format of a drawing based on a value in its display state doesn't seem damn interesting.
I'm also not sure that Dassault's computer scientists are ready for such a reshuffle of the Mises en plan (it's already one of their big weak points then...)
At least that's what I understood from your proposal (I hope I'm right, otherwise it's your Shrink who will owe me a substantial percentage of your bill).
… By the way, you owe me 120€ (well what I did myself!)
And all my condolences for the pairs of skis who suffered during your alcoholic setbacks ... (Alcoholic setbacks ... that's a funny formulation...)
Personal note:
Their " like " system is still badly done, I realized, late in life, that you just have to click on the Thumb again to cancel your vote without any other form of trial, so I had cancelled my " Like " for some proposals for which I had voted...
These TTLs are starting to cost me a lot! 
For my part, the manufacturers do not deal with translations; they request it if it is not available in the " dictionary ".
I have tested the MyCadTool DrawingTranslate tool but it does not give satisfaction because it duplicates entire sheets.
There are other problems that could be solved with this improvement: when a part is produced in several operations at several subcontractors with each time a plan that is used for the compliance ctrl: e.g.: Foundry, machining, painting. or machining, treatment, machining, painting. I don't mention these cases because we got around the problem with derivative parts, so different parts and drawing files for each step rather than configs.
yes, I didn't like it either. (On one of their old versions you could at least do a translation search on the Web... unfortunately there was only the mediocre googleTranslate at the time).
Concerning the " Composition " I hadn't thought about the machining of commercial components (it happens.) => Another thumb (well a credit, I've already used mine...).
Good evening
I think it's maybe too complicated for something that is " easily " managed with different drawings looking for the same assembly (or part).
And if you ever want to make EPDM digest this, it might be difficult (and SW will only add a function if it doesn't put the strand in these other tools including PDM).
Another important point is the ISO: your idea as stated will give you 4 or 5 different files with the same information in the title block but not quite (number of pages) and in the end different data → have two documents that have the same plan number, the same revision and not the same number of pages / the same information → loss of your ISO certification (you will still have a remark of the listener asking you to correct it before you lose it).
From the analysis that has been made, it is precisely having several plan files referencing the same 3D model that is problematic with PDM in particular: the commands copy/move the tree structure for example with the option Name drawings after their model to copy the names of the drawing files on those of the associated parts or assemblies files. With several plan files, the naming must be done manually with a significant risk of error.
Regarding this point, I am not worried. Having audited myself for the (Mastery of) Design and Development part of the ISO 9001, 13485 and 15378 standards, and knowing that it is possible to have different basemaps for each sheet calling different properties of the referenced plan file or model, this is a point that already has solutions. On the other hand, for the issue of plans in different languages, it is indeed the same document that must have the same reference. The name of the exported file will tell it the language of publication.
Hello;
They are strong, very strong at Solidworks...
The two captures below were made on the same day (today):
It took less than a month for the Solidworks teams to integrate the requests of the Top-Ten List into Solidworks 2026 while the latter is not closed ...
Hats off!
Ah! Yes, [Sarcasm] mode was enabled.