custom transaction field isn't showing the value in saved search

AI generated answer (using internal Slack threads):

****** Disclaimer: This response was generated by an artificial intelligence assistant based on previous conversations from multiple Slack channels, and may contain inaccuracies or mistakes. ****** If your custom transaction field isn't showing the value in a saved search, there could be several reasons for this. Here are some potential solutions: 1. Check the Access Tab of the Custom Field: Make sure that the view is set to None under the Access tab of the custom field. This setting can sometimes prevent the field from appearing in saved searches. 2. Check the Transactions/Records: Ensure that there are transactions/records with the selected values of the custom field. If there are no records with the selected values, the field will not appear in the saved search. 3. Check the Permissions: If the user has full access to both the custom record and custom transaction type, but the values do not show in the saved search, it might be a permissions issue. You can test this by creating a blank role with No permission, then go to that custom record and click on one of the data points that you can see as an admin but not the user. Copy the URL and then change your role to the no permission role. This will help you determine if you need to change the permission level or add a different permission. 4. Wait for a While: Sometimes, it takes a day or two for the custom field to appear in the results of a transaction search. This is especially true for new fields. 5. Check the Field ID: If your field ID is "Is Checked" and you have created it on the transaction form from customization>>new line field, then search "Is Checked (Custom Column)" in the Results tab, not in the item fields. Remember to always double-check your settings and permissions to ensure that everything is set up correctly.