Joshua D Lorenz

My feedback

  1. 7 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Wishlist » Events  ·  Flag idea as inappropriate…  ·  Admin →
    Joshua D Lorenz supported this idea  · 
  2. 15 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Wishlist » Online payments  ·  Flag idea as inappropriate…  ·  Admin →
    Joshua D Lorenz shared this idea  · 
  3. 61 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    34 comments  ·  Wishlist » Online payments  ·  Flag idea as inappropriate…  ·  Admin →
    Joshua D Lorenz supported this idea  · 
  4. 77 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    40 comments  ·  Wishlist » Contacts  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Joshua D Lorenz commented  · 

    When a user registers to an event, and populates the common fields on that event, those values should update the users profile, not just the users event registration profile.

    If a user, who already has common fields populated, registers for an event, their common fields are pulled into the event registration, saving the user from needing to populate any existing common fields.

    However, if a contact has registered for an event, completed all common fields, then goes to register for anther event, the common field answers are all blank, requiring the contact to again answer the same questions over again.

    This is confusing to the contact who believe they just created/populated a user profile on the website.

    To the same accord, an existing contact who already has populated their common fields changes a value on the event registration, expecting this will update their profiles common fields and later, upon registering for another event, discovers the value has been "rolled back" even though they updated it.

    This defeats the purpose and use of a common field - as the field should be common across the entirely of the platform, not separate for the event record and the contact record.

    WildApricot should resolve this anomaly ASAP, or at least offer the option to update the contact common fields when the event registration is completed using common fields.

    Joshua D Lorenz supported this idea  · 
  5. 15 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  Wishlist » SEO  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Joshua D Lorenz commented  · 

    WildApricot, any traction on this request? This is pretty major for us organizations relying upon events.

    Joshua D Lorenz supported this idea  · 

Feedback and Knowledge Base