> ## Documentation Index
> Fetch the complete documentation index at: https://docs.wegive.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Why the 'Map Answers To' list is empty for a checkout question saved to the Transaction

> How to fix an empty 'Map Answers To' picker on a checkout custom question set to 'Save answer to Transaction': the list only contains your own Static Transaction custom fields, so create one first, then select it and the answer is written to it on each gift.

# Why the "Map Answers To" list is empty for a checkout question saved to the Transaction

When you edit a custom question on a checkout and choose **Save answer to Transaction**, you can optionally pick a field under **Map Answers To**. If you open that picker and see no fields to choose from, nothing is wrong with your checkout. The picker is empty because your account doesn't have a field it can offer yet.

## What the picker lists

For **Save answer to Transaction**, **Map Answers To** lists only your organization's own **Static custom fields on the Transaction record**. It does not list WeGive's built-in payment columns (such as amount, date, or payment method). Those can't be filled in from a checkout question. It also doesn't list fields from other records, such as Supporter or Recurring Plan custom fields, and it doesn't list Computed fields, because WeGive calculates those itself.

Until at least one Static Transaction custom field exists, the picker shows nothing but the **Save answer only** option. The question still works. Donors' answers are kept with the gift, but they aren't copied into a field.

(If you choose **Save answer to Supporter** instead, the picker lists supporter fields and Supporter custom fields. **Save answer to Recurring plan** lists Recurring Plan custom fields.)

## How to fix it

1. Open the **Custom Fields** page in the dashboard (**Database → Custom Fields**; the page is also in **Settings**). You need an Admin or Developer role to create fields.
2. Click **Create Custom Field**.
3. Set **Object** to **Transaction**.
4. Give the field a clear **Name**, for example `Appeal Code`.
5. Set **Type** to **Static**, then choose the type of value it holds (Text, Number, Date, or Boolean) so it matches the answers you're collecting. Text suits most dropdown and short-answer questions.
6. Review and save the field.
7. Go back to your checkout's **Custom Questions**, open the question, make sure **Save To** is **Save answer to Transaction**, and open **Map Answers To**. Your new field is now in the list under **Transaction Custom Fields**. Select it and save the checkout.

If you created the field after you opened the question editor, reload the page so the picker picks it up.

## What happens after you map it

Each time a donor's answer to that question is saved on a gift, WeGive also writes the answer into the mapped Transaction custom field on that gift. You can then use the value in the places custom fields appear: the transaction record, segments and filters, exports and reports, and CRM integrations.

* Mapping applies to answers saved from then on. Don't assume gifts made before you set up the mapping were filled in. Check a recent older gift before relying on it in a report.
* Changing **Save To** clears the selected mapping, so pick the field again after you change it.
* A Transaction custom field must be **Static** to receive answers. A Computed field can't be written to.

## Related articles

* [Custom Fields](https://docs.wegive.com/external/support/settings/custom-fields.md)
* [Creating a Checkout](https://docs.wegive.com/external/support/elements/creating-a-checkout.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.