Delete POP group names broke with expression

[bradonwebb]

The deleteSOP used to take in nice expression from a table or text data, so you could combine all your object groups into a simple list separated with a space, and it would work FANTASTIC in a deleteSOP… but that expression now doesn’t work in a deletePOP? The deletePOP doesn’t outright fail, but it gives a warning and does not filter the groups

I’m assuming the intended function is that I would hit that little + - button a bunch of times and put one group name in every single field, which could be nice on occasion, because then you can use group boolean operations, but this is not really what I want. I just want to slam a text field directly into that group filter, same as it was in SOPs. That way, it’s really easy for me to dynamically filter groups without worrying about how many I have. It just reads whatever is in that [0,0] data table and filters accordingly. Best of both worlds, you could use the ± button, but also text expressions would still work in each of those field boxes.

[bradonwebb]

Here is a clean, reproducible file that shows the behavior. It could be that you didn’t design the pop behavior that way intentionally, but this kind of thing is super handy and would be great if that string box worked the same as in SOPs

DeletePOP_reproduced.1.toe (4.5 KB)

[Guillaume.L]

Hello @bradonwebb
Thanks for the report. The current Delete POP behavior is actually intended — it expects individual group entries rather than a group list. That said, we can see how supporting group lists (similar to the Delete SOP) would make certain workflows much smoother.
We’ll add this as an RFE so the team can look into extending the POP version to support that workflow as well.