All Collections
Versions 3.0 and 2.0
Implement
Platform SDK
Disable Fuzzy and Historical Matching for Category Fields Options
Disable Fuzzy and Historical Matching for Category Fields Options
Elisa Dinsmore avatar
Written by Elisa Dinsmore
Updated over a week ago

This article is for Flatfile's Portal 3.0 and Workspaces. If you'd like to check out the latest version of the Flatfile Data Exchange Platform, click here!

Flatfile uses several levels of auto-matching to ensure the option entries in your or your user’s files are matched to the appropriate values in your template.

  1. Exact matching is executed when there is a 100% match between the value in the field and the category option in your template. This is case insensitive, so “sales” and “Sales” would still count as a match.

  2. Historical matching uses previous matching decisions to match fields in new files, and is completed automatically for your user.

  3. Fuzzy matching compares the record to the list of category options and labels to find and recommend approximate matches.

Flatfile will always match exact matches for you when matching fields or options in your OptionFields, but if you want to disable historical matching or fuzzy matching for your categories in your OptionFields, you can add a flag that will disable these and only automatically match exact matches.

In the Flatfile Platform SDK, the syntax for this would be matchStrategy: “exact”. For more information about the options available for OptionFields or for deploying via the Platform SDK, visit our developer docs.

Did this answer your question?