/build/static/layout/Breadcrumb_cap_w.png
05/04/2017 570 views
Hi All,

I've noticed a few times, and more frequently now, that smart labels haven't been working very well when nesting labels. At first the labels will populate, and then eventually they'll drop all or most of the machines that should be a part of those labels.

For instance, I have a "Win Workstations" LDAP Label containing all windows workstations, then built a smart label based on the LDAP label that contains all machines with Acrobat Pro for updating. Going into the smart label itself, it displays all the machines within Win Workstations that have Acrobat Pro installed. However, when looking inside the Label Details or even at the general Label list it displays that there are no machines in the label.

Additional Info:
K1000 v7.0 This has been going on since 6.4.120822 as well.
Restrictions have been removed, and the issue persists.
I've recreated new labels in the past to remedy the situation, however, it returns later.
0 Comments   [ + ] Show comments

Comments


All Answers

0

My guess is that this has to do with the evaluation order of LDAP vs. Smart labels. However, I wasn't able to find anything definitive and didn't see anything obvious in my K1 either. In this case, I would suggest including the OS logic in the smart label so you don't have to reference the LDAP label. This workaround might not work in every situation, unfortunately :-/

Answered 05/05/2017 by: JasonEgg
Red Belt

  • So the primary reason I nest is because a huge chunk of labels are filtered in a similar way, and using the wizard is really irritating when you need to have even 10 filters. You get to the point where you only see 1 computer at a time below the list of filters. It becomes pretty clunky at that point.

    It would be cool if you could adjust the area of the window the filters can take up and then be able to scroll through filters as well. I'll probably have to put that in as a feature request.