I've had a problem for a few days to rename my configs. Let me explain, when I want to rename a config, I can't if the plan of my room is open. Also, the problem is the same if my part is in an assembly and it's open. Small detail, before when I selected my config and clicked on it I could directly name it, now, I have to go to the config properties. This problem has been present since I have access to the 3Dexperience cloud (to test), is it related? I guess because 2 colleagues don't have access to this platform and don't have any problems of this kind.
Not being able to rename a configuration while it is used in a plan or in an open assembly is normal behavior. (It's like trying to rename a file from the explorer while it's open).
for the second point I would say " yes " it's related since it didn't do it before or with your colleagues who don't have a connection 3Dexperience.La underlying question is: do you really need to connect to the 3Dexperience Cloud when your classmates seem to be able to do without it.
" Not being able to rename a configuration while it's being used in a plane or in an open assembly is normal behavior." It's noted, but why can my colleagues do it and why could I do it before? That's what I don't understand.
For the second point, as I said, it's to test. Indeed, my colleagues do not have access to the platform, for the moment. If the tests are right for us, it's highly likely that they will come under 3Dexperience as well.
Hello I think that for everything related to 3DEX it is better to make a ticket to VISIATIV support, the whole thing being in development (and for a while...). Have you tried to log out of the 3DEX platform?
Indeed, I'm going to make a ticket. I prefer to ask here first, instead of wasting time (and looking like a c*n) to the support if the problem came from me.
Which version of SW? In 2020 a priori no problem to rename the config but on the other hand you can't delete a config used in an open assembly/MEP. From memory, this was not possible on previous old versions. If your version is higher than the 2020, it's either a bug (reboot SW) or a system option (search with ' config ' in the SW settings)
Well, not quite. Indeed, historically, you couldn't rename a config if it was used. Now (I can't say since which version), it is possible to rename a config in use and the user documents of the file are updated (there is probably an internal ID for the config). And it works quite well.
I have had confirmation from the support, it is indeed the 3Dexperience. They have no way around it. I managed to get by with a macro, it's not ideal but it works and above all it's not longer.
Have a good day and thank you again for your answers!
