A user, Jay_Moore, is trying to pass custom user fields when signing on a user using DiscourseConnect. The fields, “Experience” and “State”, are not coming across. Falco suggests that custom fields created via Admin → Customize → User Fields should be passed as custom.user_field_NUMBER, not the actual field name.
Falco provides the correct syntax, and Jay_Moore confirms it works. However, Falco notes that DiscourseConnect does not currently support multi-select fields. Jay_Moore finds that while sending multiple values doesn’t work, sending a single value does.
Later, Jay_Moore has an issue with adding a user to groups using add_groups. Falco points out that the issue is due to a space between the commas in the group list.
The field name is Experience, it is a multiselect field and one of the options is Pro
I am not seeing this come across? I also have a custom field named State, which is a Text Field. How do I troubleshoot this. I don’t see anything about the custom field in the logs with discourse connect logging turned on.
Curiously I was looking into this last week, and from the looks of it we do not support multi select fields via the DiscourseConnect payload at the moment.
Did some testing and it will populate a multi select field if only a single value is sent.
Does not work - ‘custom.user_field_1’ => ‘Pro, Newbie’,
Does work - ‘custom.user_field_1’ => ‘Pro’,
This is OK for our needs. If that field is editable by the end user they can add other selections as needed.