Review Suggestions

Review suggestions in two passes:

1. Check the field itself.
2. Check the Business Central target.

Make sure the field name is specific, the line or header setting is correct, and the destination table and field are the ones you actually want for that document type.

Confidence guidance

On mapped rows, pay attention to the confidence badge:

• Green, or a very high percentage, usually means the match is straightforward.
• Yellow, or a middling percentage, means the suggestion is plausible but should be checked.
• Manual means the current mapping does not match the automatic suggestion.
• Not Mapped means Sifterra did not find a strong enough match.

The assisted mapping flow can also label suggestions as high, medium, or low confidence. Treat those labels the same way: high is usually reliable, medium needs review, and low should be verified carefully.

When suggestions are usually safe

• The field name is clear and specific, such as vendorInvoiceNo, documentDate, quantity, or unitPrice.
• The suggestion points to the obvious standard Business Central field.
• The header vs. line setting is already correct.
• You are mapping the same kind of document you have mapped successfully before.

When to stop and adjust

• The field name is vague, such as number, date, amount, or total.
• More than one Business Central field could reasonably fit.
• A line value was mapped to a header field, or the reverse.
• You are working with custom terminology or company-specific rules.
• The badge is yellow, low, Manual, or Not Mapped.

Good examples of fields that often need a second look are totals, posting dates vs. document dates, invoice number vs. order number, and any custom reference field.

Additional notes

The repo contains a separate mapping review page, including columns for Include, Confidence, and Rationale, but there is no current page action or wizard step that opens it. The visible workflow is still the normal one: review proposed fields, then review the mapped rows in the standard Field Mapping step.

The codeunit also includes a free-text field description procedure, but there is no current UI entry point for that flow. The visible product path remains sample-based.