What do you mean with "Supress"?
You could either create a Display Configuration without the Part you would like to "Supress".
Or you could use the main Display configuration use Hide // See the screenshot
No parametric modeling needs to be done for automation purpose.
Unlike features in a part document where you create a suppression variable for controlling visibility, the parts placed in an assembly can be accessed via the Occurrence object having a Visible property which is a Boolean.
Hope this answers your query.
@bshand Based on the very short and severely misspelled post, my interpretation of the question is this:
The user wants to show/hide or suppress/unsuppress parts in an assembly via automation.
A commonly used method in a Part for suppressing/unsuppressing features is to right-click a feature in the PathFinder and select Add Suppression Variable. This adds a variable to the Variable table in the format "FeatureName_Suppression". A value of either 1 or 0 can be assigned to the suppression variable.
Set the value of this suppression variable from a automation programm written in VB.Net, CSharp or C++ to 0 to suppress the feature and 1 to un-suppress the feature.
My guess is the user wants to do similar thing in an assembly i.e. show/hide parts or components in the assembly from a VB.Net program. From the automation program, the parts in the assembly can be accesses via the occurrences collection and each occurrence corresponds to a part in the assembly. The occurrence has a Visible property which can be changed to True or False to show/hide it.
I have not tried this out but inferred this based on a glance through the Object Browser in Visual Studio. Only the user can confirm if this is what s/he is looking for.
Thanks. Yeah, I got the suppression variable for parts thing. It was just that one sentence that got me.
This makes me think of the gag when you talk to fast food speaker all broken up like a bad speaker, and the order taker repeats back the order perfectly clear.
This is how you can do it and as you see there is no need to prepare the assembly:
Public oApp As SolidEdgeFramework.Application
Public oDoc As SolidEdgeAssembly.AssemblyDocument
oApp = Marshal.GetActiveObject("SolidEdge.Application")
oDoc = oApp.ActiveDocument
Dim oOccs As SolidEdgeAssembly.Occurrences
Dim oOcc As SolidEdgeAssembly.Occurrence
oOccs = oDoc.Occurrences
oOcc = oOccs.Item(1)
'oOcc = oOccs.Item("chead.par:1")
oOcc.Visible = False 'Or True