Can anyone give me a clue as to why this assembly always needs to be saved, even when first opened? The component in the assembly on its own doesn't have this problem.
Can anyone give me a clue as to why this assembly always needs to be saved, even when first opened? The component in the assembly on its own doesn't have this problem.
Thanks for having a look Glen. It's in my WPDM working folder (it's not in the vault). I tried saving it to different locations and even unloading the PDM addin but same result every time. If I hit rebuild or just save and re-open it's dirty.
Okay, when I first opened it it required a rebuild:
But after I save it, it doesn't show that message. I completely got out of SWX and back in and it opens fine now.
After just having to perform a clean install because of something similar, I'd say it's possible your installation is messed up. I don't have the diagnostic tools or knowledge your VAR does. So, before going through all that trouble, I'd send it off to the VAR.
Here's the thread I started about getting my settings back after I reinstalled:
How do I get my settings back???!!!
If you are using old templates or used Copy Settings Wizard from an old install, it can cause things like this.
What version of SW are you on Glenn? I'm on 2017 sp4.1 and this looks like it's something to do with mirrored components. I just created a simple assembly with a simple rectangle and when I mirrored the part I get the same result - always dirty.
For SW 2017 SP1 everything looks fine:
Thanks Matt. I tested this on 3 machines here with same result.
Yeah, I tested my assembly on a couple machines up here and I got the same result because we were all using the same old Custom Settings file.
Are you on subscription?
Yes we're on subscription and I'm sending this off to our var. We don't all use the same custom settings file here. I dug up another library part with a mirrored component and it shows the same behavior.
Thanks for verifying Vladimir!
Since this is a an assembly with 1 part and 2 configurations (1 config is a sub config of the other), then the way to make this so it doesn't have to be rebuilt every time you open it, is to add the "rebuild/save mark" to both configurations in the part.
Once you do that, the part no longer needs to be rebuilt.
I think it has something to do with the config data not being saved, and since the part is saved with one configuration active, it need to rebuild to create the other one.
Once you add the rebuild save mark, then the config data is saved with the part and you no longer need to rebuild it to create the 2nd config.
Dan,
I am not prompted to rebuild the part at all and I didn't have to take that step. Maybe there is something in your settings different than mine. When I switch configs, it just switches, no rebuild required:
Am I missing something or doing something different?
Thank you Dan but the assembly doesn't need to be rebuilt, just saved. I tried your suggestion and added rebuild save marks to the configurations in both the part and the assembly but I still get the same result - the assembly needs to be saved every time it's opened.
To follow up on my reply, I'm not prompted to save, even if I switch configs before closing.
Matt Peneguy wrote:
Dan,
I am not prompted to rebuild the part at all and I didn't have to take that step. Maybe there is something in your settings different than mine. When I switch configs, it just switches, no rebuild required:
Am I missing something or doing something different?
What are your settings here?
Dave Hoder wrote:
Thank you Dan but the assembly doesn't need to be rebuilt, just saved. I tried your suggestion and added rebuild save marks to the configurations in both the part and the assembly but I still get the same result - the assembly needs to be saved every time it's opened.
After adding the rebuild/save mark, I no longer need to save it when I open and close it.
Hrmm...let me dig further.
Dave Hoder wrote:
Thank you Dan but the assembly doesn't need to be rebuilt, just saved. I tried your suggestion and added rebuild save marks to the configurations in both the part and the assembly but I still get the same result - the assembly needs to be saved every time it's opened.
Dave:
Do you have this checked?
And what do you have to "rebuild assembly on Load"?
Maybe that wasn't the answer, because I just tested it out with these settings (see below) and I still don't have to save it when I open and close it (SW 2017 Sp5):
Dan,
Here's my settings:
Hrmm....doesn't make sense then.
I had verification unchecked and was set to always rebuild on load. I tried some different settings with no joy.
Dave,
Recently, I had some really screwy behavior on an assembly and had to reinstall SWX. But thinking about it, my templates may have been part of the problem all along.
So, I just checked the assembly you posted and your templates are from 2014.
It is probably not what is causing this problem, but it won't hurt to update your templates. You don't want to end up in the situation I ended up in. Having to do a clean reinstall takes a lot of time.
Did you try the Freeze Bar?
Hi Matt
These are library parts and rebuilding our library from scratch isn't really an option (I was just adding some smart features). I've seen some other issues since the Windows 10 fall update but I'm going to wait until we move to SW2018 for a fresh install if I can. I tried updating to sp5 but that didn't fix this issue or my SW Explorer problem (rename causes crash).
Didn't know about that. Is that a new feature? I'm still on 2015
I'll be using that in the near future!!! Thanks for sharing John!!!
Chris
Thanks John I've never used that. I gave it a whack but same result - assembly still dirty on open or rebuild.
It didn't need to be saved when I opened it. Maybe it has something to do with where you have it saved?