Lists - Need More Flexibility, Robustness

When creating lists, there is a LIMITED amount of data available.  All information associated with various objects should be made available. [something akin to advanced lists, but perhaps a simpler model, like the query model in EE].

For example, we need to see the decision on all of our 1,300+ applicants.  The 'Candidate list' does not let us choose this as a Column.

 

Who decided this was not important?!?

I don't think implementers are the right people to make such decisions.  I think the *only* person who can make this decision is the end-user, so the current mechanism  is insufficient.

 

 

  • john ronan
  • Jan 13 2020
  • Attach files
  • john ronan commented
    January 24, 2020 20:46

    My mistake. I think I was referring to the 'comment' on the decision of a
    candidate that was not provided in the list.
    Part of my point is simply that we should be able to pick and choose *any*
    information on an object (student, candidate, course, etc) without having
    to have a particular piece of information added by BB.

    On Mon, Jan 13, 2020 at 12:36 PM Blackbaud K-12 Ideas <
    e383579cbc2d408f393d0513-blackbaud@iad-prod1.mailer.aha.io> wrote:

    >

  • Sarah Bienvenue commented
    January 13, 2020 17:35

    Hi John, we have both candidate and school decisions as filter options and column options, we're always adding more columns and filters, and love getting feedback regarding filters and columns that we may be missing, were there any others?