RENXT Events - Ability to Add/Update Custom Fields for Event

While Event attributes in database view are viewable in web view as custom fields, there is no way to add or edit the custom fields in web view. It seems reasonable to me that if we can see the custom fields in web view that they should be fully functional. We use the Event Attribute/Custom Fields for sorting or otherwise identifying features that apply to the entire event for categorization and reporting purposes.

There is an idea open for voting right now in Ideas: “EVENTS-I-22 Attributes for Events”. Please vote for it if you agree that these custom fields should be addable/editable. “RENXT-I-7248 Allow custom field on event records” is essentially the same idea, so perhaps someone from Blackbaud could merge the two?

Comments

  • Miki Martin
    Miki Martin Community All-Star
    Kudos 5 Fifth Anniversary PowerUp Challenge: Standard Reports+ PowerUp Challenge #3 Gift Management

    @Donella Robb are you talking about from the Events record or the participant record? I am able to add options from both. Maybe I'm misunderstanding.

    From the Event record:

    c6844e03a333165c003cd242d21bad29-huge-im

    From a participant record:

    29884f1c97a798eba9e0f4902c87da7a-huge-im


  • @Miki Martin No, I am referring to the Event custom fields – this would refer to the entire event (i.e. the event is a walk/run event), not just to a participant. I was able to put the two tiles side by side for a screen capture, and you can see that there is no option to add Event custom fields. However they can be added from database view as attributes, and they then appear in web view.

    db27f5fdcfd1c09d080c245ff693124d-huge-im


  • Miki Martin
    Miki Martin Community All-Star
    Kudos 5 Fifth Anniversary PowerUp Challenge: Standard Reports+ PowerUp Challenge #3 Gift Management

    @Donella Robb well that makes more sense seeing that. I am not seeing any Custom Fields tiles on any of our events so maybe that is why I was struggling to understand. I thought we had been tracking some attributes for events but I think they're all participant-specific. Thanks for the clarification.

  • @Donella Robb While we are talking about what can't be done in web view for events…we use actions for all our events, that isn't in web view. I hope someone doesn't say “that's for the idea bank” - no, it's an often used field in DB view, it shouldn't then be an “idea” for them to decide it's not needed. Sorry, I really don't like how all this has rolled out. It's been 10 years since we converted to RE and we keep hearing we need to move to web view, but the my team can only do a few things in web view, and then we have to go to db view, so we just stay in db view. I hope the db view doesn't go away before I retire - you know, old dog/new tricks and all!

  • Karen Diener
    Karen Diener Community All-Star
    Tenth Anniversary Kudos 5 First Reply Name Dropper

    @Rose Dixon and @Donella Robb the spring Product Update Briefing for RE is today. I recommend registering to watch live if possible. If you cannot, go ahead and register and you'll receive a link to the recording. You can also review archived PUBs on the registration page.

  • @Karen Diener I am signed up. But every time I listen, it confirms the fact the those of us who do heavy database work in db view still have to do the heavy lifting there, making it exceptionally hard to even attempt to learn how to use web view. We processes over 80k transactions annually and to have to do partial work in web view and then finish in db view is not a constructive, or efficient us of our time.

  • Karen Diener
    Karen Diener Community All-Star
    Tenth Anniversary Kudos 5 First Reply Name Dropper

    @Rose Dixon:

    @Karen Diener I am signed up. But every time I listen, it confirms the fact the those of us who do heavy database work in db view still have to do the heavy lifting there, making it exceptionally hard to even attempt to learn how to use web view. We processes over 80k transactions annually and to have to do partial work in web view and then finish in db view is not a constructive, or efficient us of our time.

    I understand, and am one of those people who works almost exclusively in database view myself.

    My only point was to make sure you are aware of the PUB, since we know Blackbaud is rapidly developing webview. As has always been the case, database view will be disabled at some point and they have started making announcements to that effect. Understanding Blackbaud's timeline is important so that you can begin shifting from database-view heavy processes when necessary.