We are in the process of migrating our second site to Kinetic, one of the things i am thinking about is how could we separate the Part Classes so that Site 1 sees Site 1 Part classes and Site 2 sees Site 2? The reason behind this is because there is no crossover of part classes and Site 2 has about 5 times more that Site 1.
Has anyone looked at this previously?
It would be really impractical to hide parts from one site or the other because parts are not site specific, you would be writing a million bpms since the part record is everywhere. But, what you could do is built a quick search based on a baq that filters parts to classes assigned to the current site (based on a ud field or whatever) and then override the base search with your custom search so they would at least only see parts belonging to those classes by default when searching.
Hi Alisa hope you are well. I wasnt specifically wanting to hide parts, i wanted to only show the part classes available to a specific site. So if you were working in Site 1 and wanted to create a part, when you clicked the Part Class field, it only showed those for Site 1. Site 1 has 15 Part Classes, Site 2 has 80, so you can imagine Site 1 doesnt want to trawl through all the ones that are not relevant to them.
You can write a bpm on the get rows method for that drop down list to filter the list - there are a ton of examples of this type of filtering here