We a requirement to be able search multple Item types using a single Query and as well as exposing properties on BOMLine.
Is it ok to add 4-5 attributes at ItemRevision Level and hide them. Enable these properties only on subclasses where these are applicable?
Is it a good design?
Any lead is really appreciated
In my experience, if you only add at a lower level, at some point in the future you end up having to put them on a higher level, or on another class at the same level because the business has changed direction for 1 reason or another.
I'm no expert on performance, but in my opinion it wouldnt impact performance much if at all.
I build an abstract item to hold all my custom item types. I will do this at Design, Part, Document, Item, etc. Each Item Type that I'd like to modify gets an abstract class then a custom Item Type. I've been burned changing anything on the OOTB Item Types, so I just won't do it any more. This abstract item is where I put common attributes for all my custom item types. Then add additional or hide from the abstract on each item type as needed. 4 or 5 should be okay. 50 would be too much.
Mercury Digital Services
Thank you very much,
Even we are leaning towards the same set up. Having abstract class for custom Item Types which we want to modify or have common behaviour.
Do you have any rough estimates regarding performance impact of adding attributes on OOTB types? Some one from Siemens suggested us to add attributes on ItemRevision. But we believe it is not good idea as we faced issues in the past .