Only the first entry working with Multiselect fields when `User first logged in` Trigger used

This appears to be a regression, as it was working a few months ago.

From this discussion:

Description

When utilising the Adding users to groups through custom field automation with the User first logged in Trigger, Multiselect fields aren’t being handled correctly - only the first entry seems to be utilised by the automation.

Of note, the User first logged in Trigger is working just fine with Text and Dropdown fields, and also with Multiselect fields if the user only selects a single option.

Also, the automation appears to be working fine with Multiselect fields when a Recurring Trigger is utilised.

Impact / Workarounds

The impact of this bug is that complex group allocations via signup are not possible. These are highly useful for forums with significant specialist content and/or private areas which aim for a smooth and personalised onboarding.

The workaround is to switch to a recurring trigger. Unfortunately, this comes with a trade-off between signup personalisation delay and site performance, depending on the trigger timing. And we all know just how vital first impressions are!!!

To repro:

  1. Have several groups suitable for testing (two minimum), each with a Full Name
  2. Create a User Custom Field, choosing Multiselect
  3. Add the Full Name of your test groups as Options
  4. Add an Automation with Add user to group through User Custom Field
  5. Select User first logged in
  6. Input the name of your User Custom Field from step 2
  7. Sign up with a test user, selecting all options in your test field
  8. Check the group allocation of the new user
4 Likes

Hi @Nathan - do you see a solution to the problem with group automation no longer working in this plugin?

Not sure what you are asking, Paul. The two are unrelated. This plugin cannot be connected to User Custom Fields at present, and I don’t think it will be on the roadmap at present.

It might be worth asking nicely for it to be a feature though as it is quite similar in many ways and I can imagine it playing nicely with the Boolean UI.

On the other side, the functionality already exists in core (albeit currently a bit broken for multiselect fields).

1 Like

OK, I guess that answers my question.
I was wondering whether this plugin might offer an alternative way to do the same thing that group automation used to do, before it broke; namely allocating users to groups based on criteria supplied. Yes, criteria involving custom user fields would be pretty essential in my case, so a show stopper if that is not possible currently.

Yeah, that’s not going to happen, it would make the plugin overly complex.

1 Like

I’d encourage you to gently advocate for that to be fixed instead!

Understandable!!! Thanks again for the great work with this plugin. It has been working flawlessly for me so far.

Hi @nathank I already did, and a bug topic was created - but the bug topic was moved back to the originating thread by a moderator, with the suggestion to create a new bug topic subject your ability (in particular) to reproduce the issue apparently (I have already reproduced it myself)

Ah yes, and then I did a ‘proper’ bug report:

Have now interlinked them all up nicely!

Thanks Nathan. I can repro on my own instance too. I’ve been testing the custom field automation and the multi-select groups functionality is indeed not working as expected - only the first group selected by the user is automatically joined.

image

3 Likes

For me, no group is showing as being explicitly joined, no matter what the selected custom user field is showing

The ‘Custom’ groups field remains unpopulated, when it should be showing the group name or names selected via the custom user field