Fill other fields from the same list row

At the end of this guide, when Paige identifies a document's vendor it also fills that vendor's number, GL code, or any other column from your list, so nobody types them and your export carries the IDs your accounting system needs.

Take a vendor list with three columns: Vendor Name, Vendor Number, and GL Code. Paige reads the vendor's name on the invoice and finds that vendor's row in the list. The vendor number and GL code usually aren't printed on the invoice, so Paige copies them from the same row into the Vendor Number and GL Code fields.

• One field finds the row. This is the matching field, for example Vendor Name. Paige compares its value with the list.
• Other fields copy from that row. Each filled field takes a different column of the matched row, for example Vendor Number.
• The filled field runs after the matching field, so it always uses the matching field's value from the same document.
• When no row matches, the filled field follows its no-match choice: keep the value AI read, or stay blank.

A field is filled one way: either standardized with a list, or filled from another field. Choosing one replaces the other.

• The list's file must include the column you want to copy. If it doesn't, update the file with Replace file… in Lists & Standardization, as described under "Manage your lists" in Standardize a field with an approved list.
• A column set up as other spellings for the list isn't offered as a column to copy. If you need it, remove it from Other spellings we should accept first.
• The document type needs a field to receive each value. Add one with Add Field at the bottom of the Fields list if it doesn't exist yet.

What you should see: in the Fields list, the field carries a Filled from another field tag.

When a field is standardized with a list whose file has more columns, its details panel offers to use them. It reads, for example, "This file also has Vendor Number and GL Code. Once Paige matches Vendor Name, it can fill other fields from the same row."

Use this route to add the same fill to several document types without opening each one.

What you should see: a new row under Where this list is used whose result reads Fills followed by the field name and the column it copies. Changes on this page are saved right away; there's no OK to click.

• The list's settings carry over. A fill matches the same way its list does: a Names and text list allows small differences, and a Codes and identifiers list needs every character to match. The fill's settings on the field show which applies: Small differences are allowed or Every character must match. To change it, change the list's kind, as described under "Choose how strict matching is" in Standardize a field with an approved list.
• Fills listed on their own. A fill that appears under Lists as its own entry, tagged Fills another field, has its own setting. Select it and answer Should Paige allow small differences when matching Vendor Name? with No - match every character or Yes - allow small differences.
• Ties. When several rows could match, the filled field has its own tie-breaker line, starting No tie-breakers., that works the same way as on a standardized field. See "Break ties when several rows match" in Standardize a field with an approved list.

A column of a line-items field can be filled from another column of the same row. In Line Item Columns, under the column you want filled, expand More ways to fill this column, then under Fill this column from another column click Set this up. Choose the list under Fill it from this list and the matching column under Lookup using column. For example, fill each line's GL code from its item number.

• On the field: click Change on the line that says the field is filled from the same row, then click Stop filling from another field. Click OK to save the document type.
• In Lists & Standardization: select the list, find the row under Where this list is used, click its trash icon (or Remove), and confirm with Stop.

Contact Ademero support and include: