Thanks all. I tried "*configuration name" in the rules..
It solved my problem. But it deletes all other configurations..
Now, that is not my serious issue.
Thanks for everyone.
I'm sure this could be related to rules. Try going thru them one by one and see if you can debug else share the files here to check.
You can also try making some dummy files (if can not share the files) and see if you can replicate the issue.
The answer depends on what rules you have captured, and how you are driving your components, as there could be a few different reasons for this, including:
- Whether you are simply trying to change the configuration of a component in the assembly without driving a new version.
- You may have previously driven a version of a model in the Cu configuration and DW is simply re-using it instead of driving a new one in the Al configuration.
The answer might be to use a different approach to your model rules, or it might be an issue with the rules themselves.
Thanks David. I have checked the rules, even spelling for the configurations. All were right. For example, in my case I have 20 parts in a assembly. I have created first rectangular part and given a name. And remaining 19 parts were the same rectangular parts but differ in lengths. So, what i did was copy, paste the 1st part and renamed it individually. So, obviously, if i did anything wrong in the 1st part it would reflect in my other 19 parts. I ran an automation which have 30 Specific names for every part and every part should change to Cu configuration if i select Cu in Input form. But here, 15 parts were responding right. remaining were not.
I tried replacing the misbehaviour parts. Still no luck. So, i have used "*Configuration name" in the configuration rules. It works for me.
In my automation Each and every automation creates an individual specific names for every driven parts according to the inputs. I'm sure i have not entered the same inputs twice. Because i have a "note" in my user form which popups when i entered the same inputs as previous one and the files relating to them are still existing in the desired location.
So, there will be no chance of re-using the driven parts.
Dave's suggestions above are good ones - I would suggest that it is likely that the File Name rule does not result in a unique value and therefore DriveWorks is simply using the existing model rather than creating a new one and driving the configuration.
DriveWorks Solo does not overwrite existing models, to see any changes, the file name must be unique. For your information, DriveWorks Pro can control whether an existing model is overwritten or not.
Separate to this, I would advise that you created and captured a Custom Property in the model called DWMaterial. Within DriveWorks Solo you can then write a rule that results in the name of a SolidWorks Material. DriveWorks Solo will then apply the material in this custom property. This is a much more flexible and scalable method for driving the material of a component in SolidWorks.
More information about driving the material of a model can be found here - How To: Drive the Material of a Part (DriveWorks Documentation)
Hope that helps
I have not tried DWMaterial custom property. This sounds good and hope it will work. Thanks for the informations Chris.