I've read some older posts on this topic and wondering if there is yet a way to get inactive records to pull on lists? I need to be able to.
Thank you!
Hi Jennifer - there's a setting in T_Defaults - Inactives in List. Set that to Yes.
Thank you! Is there anyway to add an option to criteria to pick and choose when we want to include inactives?
Came back to say I don't see "inactives in list" or anything similiar...would it be called something more obscure?
Yes, you can then use criteria in your list to take them out if you don't want them in.
I don't see anything about inactives on a list. I tried to search in the T-DEFAULTS table by "list", "Inactive" and "include"
Strange. We have an entry in T_Defaults - ID 82. The field name is Inactives in List and our default value is set to Yes. I just checked the documentation for T_Defaults and this entry is still listed there.
I'm probably blocked from it. I see ID #s missing. I will ask our IT guy. Thank you!
I don't think you can be blocked from individual rows on a System Table. More likely this configuration was just never entered into your table. We come across this from time to time: not all configurations are required to exist.
Generally correct. It is not possible to be blocked on individual rows on a system table that is not a View. There are at least a couple standard out there, and Katie Lachance-Duffy has a wonderful customization that we are also using to use local views. But that is the only way of which I know to hide individual system table rows.
As a consortium, I would love to see local view options become the standard, though. Seems like a logical step to me.
thanks guys! So does this mean I have no way to show inactives on a list?
I would check with support, but I think the missing configuration variables can pretty simply just be added in. Unless you know of any different, Gawain Lavers?
Nope: just add it as specified in the documentation.
Note: you many not personally have Edit permissions on the table, which you would need to bring up with your IT person. But otherwise just add in a new row.
Now: this is a big global change that will affect all users, and overwhelmingly people don't want inactives in their lists, so every List user would need to be on-board with this change.
If this is widely desired, there is always the Constituent/Inactive Flag list criteria.
If not, here's a thought: create a simple extraction instead. Extractions do not filter out inactives by default.
It worked!!
I am the primary list puller, but I will bring it to our meeting today and let them know this is how it's set up. So if they wish to exclude the inactives they can add the flag in list criteria.
Seconding what Gawain said. it is REALLY easy to forget staff members and/or forget in the future that you are including inactives in your lists. If you are not comfortable with it being a full on global change, better to use extractions, in my opinion.
If extractions are too scary, the other option is to create your list like you normally would, click "Show Query" and then take out the "where a.inactive = 1" part, but usually SQL is scarier to people than an extraction would be. Especially since, sometimes you would need to remove the "where", sometimes you would not, and sometimes you might have to remove an additional "and". But it is theoretically possible to do it that way, too.
since you lost me at "Show Query" I'm thinking extractions are less scary...or excluding inactives from list...but I will get a vote today.