Action Network Help & FAQs

Viewing and managing questions and custom fields

You can view and manage questions and custom fields for your groups by clicking the "Questions" link in the "Start Organizing" menu in the right column. After you choose the group you want to view questions and custom fields for you'll see a list of questions that already have been created for the group up top, and custom fields for the group below.

You can add a new question if you have the permissions to do so by clicking the "Add New Question" button. You can also edit, hide, and delete each question if you have the permissions. Otherwise you can view or hide the questions but not edit or delete them.

Editing a question will change all future questions that are added to forms, but will not change questions that have already been added to forms.

Deleting questions will not delete the underlying data and custom field columns associated with that question, only the question itself.

Hiding the question will remove it as an option when making actions.

If your group is part of a Network, you can also share a question with your child groups.

Adding a question that stores in custom fields instead of tags will also create a custom field to store that question's data, if it doesn't already exist. See here for more information on how questions relate to custom fields. You can also create custom fields via the upload process, when editing or adding activists individually, when making blank questions on forms, or over the API. Custom fields do not have to be created first, you can just start using them and they will show up in this list.

However, you can hide custom fields by clicking the hide button to the right in the custom field list. Hidden custom fields will not show up anywhere in the administrative interface, but data can still be stored in them (via questions on forms, for example), and the data that's already in them is not deleted.

You can unhide custom fields and questions by clicking the "View Hidden Items" link at the bottom of the list and clicking "Restore" in the custom fields and questions sections.

If your group is part of a Network, you can syndicate custom fields to child groups.

If you syndicate a custom field to a child group, the value for the field on an activist is now locked. If you change it in one group (either the parent or any children), it will change in all of the others, rather than going up from child to parent as it would normally do in a network.

When you syndicate a custom field that already exists on child groups, activists on those groups will assume the value for the field of the parent. The syndication will "cover" the already existing value. If you later unsyndicate, that old value will re-appear.

Custom fields can also have optional validation, which are regular expressions that validate the data coming into the custom field, and reject data that doesn't match. To add a validation on a custom field click the "Add Validation" button next to its name in the custom field's list. To edit an existing validation or remove it, click the "Edit Validation" button.

In the window that opens you can add or edit the validation for the field, or remove validation. Start by choosing the validation you want to use from the dropdown menu. We have some built in validations you can use for things like US phone numbers (ex: 465-985-3864 would pass validation, 645-9378 would not) or dates (06/09/2010 would pass validation, June 2 would not), or you can write your own regular expression to validate in a custom way. Enter a description as well, so you know what your validation does. Click save to save your validation. The field in the custom fields list will note that it has a validation and show your description so you remember what the validation does.

If a custom field has validation it will not accept any data that doesn't match the validation. On front-facing places where custom field data is entered, such as petitions or other actions that collect custom field data or when adding or editing activists individually, if the data does not match validation a red error will appear and the form will not be allowed to submit until the error is fixed. You should be sure to explain what format you require on actions like petitions, so your activists know what to do when they see the red error. On backend-facing operations like the API or uploads, data that doesn't match the validation will be discarded and not added to an activist's record.

If a field is in a network, the validation only applies to the field on that group, so the data could be accepted on a child group and rejected on a parent or vice versa if different validations are applied at different levels. If you have syndicated the custom field to children (rather than the question), then validation will apply at all levels.

Have more questions? Submit a request