Summit-Events-App icon indicating copy to clipboard operation
Summit-Events-App copied to clipboard

[BUG] - Global Picklist Values on Question Object

Open rdblake21 opened this issue 2 years ago • 1 comments

Describe the bug When creating a custom question is created on the question object and the field type is picklist, there is an error when the mapped picklist value is set to a Global Picklist Value Set. It seems to be a permission or functional issue difference with Global Picklist values in the "SummitEventsRegisterGuestsController.cls" that are not in the SummitEventsAdditionalQuestionsCtlr.cls. Utilizing a Global Picklist value on the registration record field seems to be the issue when on the Additional Question Page, but works when on the Register Guest page.

To Reproduce Steps to reproduce the behavior:

  1. Create a new picklist field on the Registration record with the values associating to a Global Picklist Value set.
  2. Give appropriate access to permissions set associated to the Registrant User
  3. Create a Custom Question record with an Registrant Type of "Registrant"
  4. Complete the rest of the fields for the Registrant to be able to answer the custom question on the Additional Question page.
  5. Be sure the Event record is display Guest to test that this works for Guests and turn off when testing the Registrant.
  6. Register and see error.

Expected behavior Expectation is that the question appears on the Additional Questions Page similarly to the Guest Registration page.

Screenshots Guest Question Experience with Global Value Set image image

Registrant Additional Question Experience with Global Value Set image image

Note that the permission set is not the issue as you can see the values for the other Registrant Type.

Additional context This is a known issue and the current work-around is to not use Global Picklist Values. This will be fixed in the next release.

rdblake21 avatar Jun 06 '22 18:06 rdblake21

This is also seeming to happen while packaged with standard picklists. Thad is looking into this and may have a quick fix already.

rdblake21 avatar Jun 17 '22 15:06 rdblake21

Included in beta release 0.28.0.1

tcdahlberg avatar Feb 16 '23 00:02 tcdahlberg

Included in production release 0.28.0.2

tcdahlberg avatar Feb 17 '23 18:02 tcdahlberg