TOPIC:

In the past, using the *RoleName* feature to indicate a single user sign-up role having multiple entries on the agenda, never included seeing these subsequent agenda entries being included in the role report. Today I was running a role history for myself and saw not only my Toastmaster sign-up role, but the subsequent *Toastmaster* Calls for Speech Objectives agenda entry. The good news is that it seems to only count one subsequent entry (there are actually 4 on the agenda), but it didn't used to include these *xx* role titles at all. Given the enhancement option to individually mark roles on the agenda as exempt from the role report; am I now going to have to go edit each of the 15+ agendas I just created for 2021 to suppress every *xx* entry on each agenda? It would seem to me that any multi-entry role with asterisks included in the role title should be ignored in the roles report by default since it's a single user sign-up role. Did I miss some other enhancement that's contributing to this issue?

Thanks in advance for the assist
Trish B
Club 1853 & 740544

Need more specifics to investigate...

Ok, profile has been updated and there are attachments to the original post that provide a visual of the issue.

I believe the issue is that you are mixing conventions (being inconsistent). Your initial "Toastmaster" role is not "*Toastmaster*", but the asterisk version is used elsewhere in the same schedule.

Let me see if I can easily make the code support the mixed usage... no guarantees... this usage is referenced many places.

As expected, the code does not really support mixed/inconsistent usage of the asterisk/keywording functionality. It is an all or nothing functionality... you cannot just use it "here and there"... you need to use it for *every* occurrence of the keywords regardless of how they show up in the roles. This is necessary to allow properly handling a wide variety of scenarios.. for example, some people use both keywording and numbered role functionality together. There are a lot of subtle cases which complicate the code for this functionality.

I created a test agenda to test my theory... The first screen shot below is with every occurrence of Toastmaster using asterisks. The second is with the initial Toastmaster not using asterisks. This just shows that inconsistent usage is not really supported by the code (in many places).



With no asterisks on the initial Toastmaster:


You have to use the functionality consistently.

BTW, this is a good example of why I do not really like the funky asterisks notation and "keyworded roles" functionality.

One of these days, I will implement role tags functionality where you would set tags for roles that you want to be considered to be the same people. e.g., all roles with a role tag equal to "TM" (short for Toastmaster) would be set to the same person for sign-ups. Then we can ditch the asterisks and the confusion with them altogether.