Add customer list as filter in Saved Search

Step One: Create a custom transaction field.

1. Type = List/Record
2. List/Record = Customer
3. Store Value = Checked
4. Applies to: Sales (any other transactions you deem necessary)
5. Display. Subtab = Main
6. Display Type = Normal or Inline (your choice)
7. Help = This field’s value is sourced from the client record (some other explanatory text)

Step Two: Create a workflow to populate your custom field (Step One)

1. Record Type = Sales Order (or invoice or any other transaction you want this to work on)
2. Events = On Create
3. Trigger Type = All
4. Save
5. Create a State
6. Name it
7. New Action = Set Field Value
8. Leave Contexts as is (or unselect Contexts as necessary)
9. Field = The custom field you created in Step One
10. Value = From Field, Record (JOIN FIELD) = Current Record
11. Field = Customer

Step Three:

1. Modify your saved search to include your custom field as a filter
2. The field will now be a drop-down list displaying all customers

Point to consider: The above will work on all newly created transactions but will not impact existing transactions. Thus, you will need to update existing records and this is the one-time upfront work I mentioned earlier. The easiest way to do this would be via a Mass Update.

Step Four (Upfront work to update existing records)

1. Create a Mass Update
2. General Updates
3. Transactions
4. Choose the Transaction(s) you want to update
5. Add Filtering Criteria as necessary
6. Expose the Fields as necessary on the Results tab
7. Mass Update Fields
8. Check the box next to your custom field
9. Leave Value blank
10. Formula = Field, Customer Main Line Fields
11. Customer Main Line Field = Company Name
12. Preview
13. Review the list and ensure these are the records you want to update

• Only update a few records initially to ensure expected behavior
• Once you have verified behavior, then update the remaining records
• All existing transactions will now have the custom field populated

I hope the above suggestions are useful. But I cannot stress enough the importance of only testing this solution in a sandbox account or other test environment like a development account. Do not implement this in a production account until you have thoroughly tested and are happy with the results. Finally, I am just a fellow user providing my suggestion and it is entirely possible there is an easier and better way.