Yeah…not really a bug I guess but definitely not ideal. Best you can do is create two configurations for your template or have a sheet metal template with the flat configuration already in place.
Maybe you could submit as a bug. If you have two configs and add the display mark to both, then delete one so there is only one config, then add a second config back, the first no longer has the display mark.
I’ve noticed this illogical behavior as well, don’t understand the point of this function either.
With the function Mark for rebuild when saving it behaves exactly the same.
I have also tried to add the markers for the standard configuration already in the template. But if there is only one configuration, the function is not available.
Next, I tried to trick the system by creating a second configuration, setting the markers for the display status and for the rebuild, and then deleting the additional configuration. Unfortunately, the markers disappear in the remaining configuration again…
I have to check if it is possible to add the markers to a single configuration with a macro and then save it as a template.
But all in all, this is again a huge effort to find a workaround to make an insufficiently thought-out function usable.
Thank you jcapriotti & Hansjoerg for re-creating the same thing that I did & confirming that I have not gone mad.
I did the same & was very frustrated because I am not willing to create two configurations for parts that do not need more than one. I guess I’ll have to live with it for now.
Just an FYI, we are going away from having the Rebuild Markup as a default for all configurations and instead instructing users to do a Rebuild All Configurations before the final save. Reason for us is we have some automation and we are experiencing very long save times when saving an assembly where it decides to save some of the part/sub-assy files and has to rebuild a lot of configurations on every save. This is also related to Windchill so you may not have the same issue.
Try the following codes (the codes will add display data mark to each config in active model file)
Option Explicit
Option Explicit
Sub main()
Dim swApp As SldWorks.SldWorks
Dim swModel As SldWorks.ModelDoc2
Dim swConf As SldWorks.Configuration
Dim swConfMgr As SldWorks.ConfigurationManager
Dim configNameArr As Variant
Dim configName As Variant
Set swApp = Application.SldWorks
Set swModel = swApp.ActiveDoc
If Not swModel Is Nothing Then
If Not swModel.GetType = 3 Then
Set swConfMgr = swModel.ConfigurationManager
configNameArr = swModel.GetConfigurationNames
'Set Large Design Review marks for all configurations to true
For Each configName In configNameArr
Set swConf = swModel.GetConfigurationByName(configName)
swConf.LargeDesignReviewMark = True
Next
swModel.ForceRebuild3 (False)
End If
End If
End Sub
You would have to put that scripted code into a Task (using the SWTaskAddIn & PDM Professional). Then during your transition, you can add an action that triggers the Task you’ve created.
I’ve got the task created in the admin tool in PDM but I’m unsure on how to modify it to get it to work as it fails every time during the transition. I’m guessing it needs some additional code but I’m unsure on what or how to add it. Thanks