1 of 1 people found this helpful
I presume the 50-60 "is one of" entries are because these the consumables at the lowest level of the category tree?
If you are on 7.3 or later you could maybe use calculated attributes to lesson this impact.
For example I have 4 levels of categorisation and it was problematic for me that I could only put criteria on either the highest level (in tree) or the full path.
So what I did was create 4 new attributes ("Level1" - "Level4") on the Category Business Object (In Incident in my case) and set them to be calculated.
ie for Level 1:
Calculation: import System
static def GetAttributeValue(Category):
Level = @/ - /.Split(Category.FullName)
if Level != null:
Value = Level
Value = ' '
Note here that split array ("Level") starts at pos zero (0) in example above so for Level 1 use 0, Level 2 use 1 etc etc to extract the correct element.
Once you have these setup you can then use in your query criteria.
Thanks for that ,I will give that a go , sounds good.
I gave your solution to our senior service desk crew but they couldnt understand it. I am away from the office for this week and next but was wondering if you could give me any help as to setting this up.
They have never tried anything like this and any help would be great.
I can do basic queries but leave this type of stuff to them.
Cheers for all your help.