Event ID as a top-level option when creating a new Event

We require EventIDs to be readable and to use certain conventions, so that we can double-check what's being pulled into BBNC and to use the IDs in reporting instead of the (sometimes extremely long and very different) official event name. The current Add Event process requires us to add the event, then go back to edit the event to modify the EventID. This extra step will make it less likely that my staff will remember to enter a correctly configured EventID when adding events in RENXT, especially since it is top-level basic information along with the Event Name, Event Date, and Event Type.

  • Keri Barnhart
  • Sep 6 2019
  • Reviewed: Voting Open
  • Attach files
  • Tara Sawchuk commented
    15 Oct 01:07

    Some might comment about other fields for categorizing events; we do use all of those but also prefer to keep our ID naming convention. No reason not to make this editable when they no doubt still have their system record ID which remains a unique identifier that's not editable.

  • Elaine Tucker commented
    14 Oct 18:52

    we also have a specific id that helps define the event