Create Mappings

There are three practical ways to create field mappings. Most teams use more than one of them during setup.

Bulk add from a table

Use this when you already know which table you want to populate.

What it does:

• Lists fields from the selected table.
• Lets you choose several at once.
• Creates one mapping row per selected field.
• Builds a starter extracted-field name from the Business Central field name.

Example:

• You bulk-add fields from the purchase header table.
• The page creates rows for fields such as invoice number, document date, and location code.
• You then adjust the extracted-field names to match your actual sample data if needed.

Auto-map standard fields

Use this after you already have mapping rows but some destination fields are still blank.

What it does:

• Looks at the extracted-field name.
• Compares it to likely Business Central fields.
• Fills in the table and field when the suggestion is confident enough.

This is helpful for common names such as:

• documentDate
• invoiceNo
• vendorNo
• quantity
• description

Auto-map is a starting point, not a final review. Always check the results.

For more detail on the suggestion tools, see Smart suggestions.

Manual mapping

Use this when:

• the suggested result is wrong
• the field name is unusual
• you need to map to a less common table or field
• you are working with line values and want precise control

On each row, you choose:

• the extracted field name
• the Business Central table
• the Business Central field
• the data type
• any optional transformation or default value

Manual mapping is the right finish step even if you started with bulk add or auto-map.

A practical pattern

For most analyzers:

1. Bulk add the fields you want from the target table.
2. Run auto-map to fill the obvious matches.
3. Fix the rows that need manual review.
4. Add any special cases by hand.

Then review header and line behavior in Map header and line fields.