Custom file types based on .XML, .TXT, .HTML or .JSON that are defined by filename and extension can be automatically detected and imported. Once defined, the definition can be used to import that file type in batches when creating a job.
Important
Custom file types are matched automatically by filename pattern whenever a job is imported with set to (in the API, fileImportSettings.fileFormat left unset). This match takes precedence over any project-level or job-level file import settings, including JSON key filters, even when those settings were configured intentionally for that job.
To bypass a custom file type match, explicitly select in the user interface, or set fileImportSettings.fileFormat (for example, json) in the API request, instead of leaving it on .
To add a custom file type, follow these steps:
-
From the Settings
page, scroll down to the section and click on Custom file types.
The page opens.
-
Click Create.
The page opens.
-
Provide , and .
If a specific file name is provided, only files matching that name and extension will be imported.
Example:
-
Click
beside the file type to provide default import settings.
-
Click
beside to define encoding if required.
-
Click Create.
-
The definition is added to the list of .