Best ways to learn logic needed to build Groups?

​@JKolodner - you may want to do known targeting runs to help you get to where you need to go.

What do I mean by that?

Well lets say that you need to get “people in this job/job code from these departments”. If you have a census file you can:

• with the census file
  • use a pivot table to pull at those parameters on the fly
  • that will give you a count
    • I like the use of a pivot table here because it can nicely show you the who is in the logic you just pulled by clicking on a total.
• setup an automatic group with the parameters
  • export to csv the group
  • see if the numbers and people from your pivot and group are the same

The grouping logic in Docebo is a literal engine...so you are using “ands” and “ors” when you tell Docebo that any one of the conditions can exist (“or”) or all of the conditions must exist (“and”) when you develop your condition logic. The rest are set at the condition level and there are some subtle nuances to them, but for the most part it is equal to, not equal to and contains are your key parameters.

Contains does a wonderful job to simplify the condition when you have many that match because of a few letters or numbers that could be across many.

Thanks ​@dklinger - that’s more or less what we are doing. We’ve encountered some challenges along the way with those “ands” and “ors” and I’m hoping that there are some resources we can find that will help step us through the logic creation process.

​@JKolodner I’ve always found that troubleshooting groups needs to be KISS :-) Complex groups are very difficult to troubleshoot, but ​@dklinger idea of having a census is really good. I’d put the order of the sets from the “biggest” to the “smallest”. Biggest collects the most users, then smallest refines the collection.

I usually start with the filters under User Management making sure to only use the options that match what Groups can do; for example, Groups don't have an option for “is empty”, so you shouldn't use that. Once I have her filters in place, I can export the results and use that to check the group once it’s built

I’m finding KB articles such as: https://help.docebo.com/hc/en-us/articles/360020084100-Managing-groups#h_01H9SXAX2B6MTGW25C0H9YBC03

I’d like to know what kinds of limitations people are experiencing - when do conditions not work the way you expect? how to avoid pitfalls?

​@JKolodner - the most common challenge that I have seen when people try to construct logic with the tools is something that is not written correctly with allowing all conditions needing to be met versus one condition. I so definitely do not know enough SQL to say I am well versed at it - I bet you many of the other older timers are, BUT another common error that I called out is with contains versus equal.

Another one that could sneak up on a person is that you can enter up to 10 values with certain conditions - giving you a way to call to “an array” of sorts.

The grouping engine also went through a UI change at one point. So anything not showing that it is “a selected” value - needs a hard return on your keyboard. This is like when you are working with the setting up to notify in the scheduler portion of New Reports.

OH - one last thing - on very complex spreadsheets, the most common error? Is that people do not do a correct copy/paste. They attempt to do a copy and paste from values that are already filtered to get to a subset of a subset.

Instead a better operation that a person should use is the paste special tool to help get the values that are selected only

I have made many of an error like that when I was moving fast.