Currently I deleted the report text node to remove material report but I cannot find the option/ switch to remove Part ID in the ISO image.
Is it a way to hide Part ID in Stress ISO?
To remove PARTID, one way is to rename the cell from lisocomp.cel list. It will be specific to stress style folder only.
Image with PARTID:
Image without PARTID:
Hope it helps!
-Regards | Rahul Kumar
Product Engineer – Global Technical Support | Community Moderator
Yes there is. In rep_sortgroups.txt add a section (as high up as possible) that catches the components that shouldn't get a part ID. The below example would target supports. The SKIP = 1 tell OPIM to skip these
SORTGROUP = SKIP RULE = EC_CLASS=SUPPORT SKIP = 1
You can still report on the skipped items
Answer Verified By: Rahul Kumar
Just what i was looking for standalone OPIM. I wanted to avoid the partid on components with State = Existing (a custom value we added equivalent than "for demolition"). This worked precisely as expected! Thanks Frank!!
There are many ways leading to Rome, another path:
When you add additional STATEs you can make that state behave like FOR_DEMOLITION.
In the openplant supplemental isometrics isoextractor schema in the PLANT_BASE_OBJECT class in the "Default Bill Of Material labels" section there is an entry for when a component is to be targeted as existing (and thus not get a partID)
IE_EXISTING = IIf(IM.Match(this.STATE,"EXISTING","FOR_DEMOLITION",""),"1","0")
Excellent Frank. do you happen to know how could i avoid getting cutid for components with State=EXISTING? i've managed to exclude them from reports/bom list and avoid the cutid label placement, but i couldn't avoid getting the component assigned a cutid. For this reason, i get skipped letters in the PIPE CUT reports. Thanks!
The solution for this is in the previous post. If you make sure that IE_EXISTING is set to 1 for the EXISTING state as well then OPIM will not see those item as reportable, they will not get a cutid, partid etc. If you need some help here let me know
Excellent Frank. Your suggestion solved the issue as expected! Many thanks for taking the time to help me!