Limitations of Segments DQL Like Filter

[MarwanC]

One of the most frustrating parts in segments is limiting the way we use the DQL like filter in the segment definition, we developed in our organisation the concept of super segments where we combine a number of segments using the 3D icon offered by the tool, however, this is falling short in all aspects, we tried also in the filter to combine the OR or the AND but we always hit the 10 limit, is there any way to increase the size on the tenant itself to more than 10 - e.g. (tags = "app.code:app1" OR tags = "app.code:app2" OR tags = "app.code:app3" OR tags = "app.code:app4" OR tags = "app.code:app5" OR tags = "app.code:app6" OR tags = "app.code:app7" OR tags = "app.code:app8" OR tags = "app.code:app9" OR tags = "app.code:app10" OR tags = "app.code:app11" OR tags = "app.code:app12" OR tags = "app.code:app13" OR tags = "app.code:app14" OR tags = "app.code:app15" OR tags = "app.code:app16" OR tags = "app.code:app17")

[Julius_Loman]

@MarwanC  tagging in Gen3 apps (which use segments for filtering data) use different concepts - primary grail tags  and fields. In long term, you should adopt your environment segmentation to this concept (yes, it might be painful depending on your case). Basically, tagging in Gen3 is taken from the source of the data. See, for example, my post from yesterday.