Since there are many export definitions in the program, sometimes it is needed to have prepared sets of them for different cases. It is possible to save them to export definitions file and preload them before exporting when needed.

Export definitions file is an XML file which contains export options. The options are divided into several sections like it is done in the interface of Export dialog: format specific options, options of detail logging, error handling options, and command line specific options. The file may also include field or table mappings. Every section/option is optional.

Example of export definitions file

<?xml version="1.0" encoding="UTF-8"?>
<-- My Access-to-HTML export definitions -->
<ExportSettings>
  <FormatSettings>
    <Items>
      <TargetFormat>HTML</TargetFormat>
      <IncludeColNames>1</IncludeColNames>
      ...
    </Items>
  </FormatSettings>
  <RecordLogSettings>
    <Items>
      <RecordLogFileName>C:\ExportLog\2019\Records.log</RecordLogFileName>
      <RecordLogExpression>"Row": <ROW_NUM>; "Field1": "' + to_string(dataset_field_val(1, 1)) + '";'</RecordLogExpression>
      ...
    </Items>
  </RecordLogSettings>
  <ErrorHandlingSettings>
    <Items>
      <ErrorHandlingType>Cancel</ErrorHandlingType>
      <CriticalErrorCount>20</CriticalErrorCount>
    </Items>
  </ErrorHandlingSettings>
  <CommandLineSpecificOptions>
    <Items>
      <CmdSilent>0</CmdSilent>
      <CmdOpenTarget>1</CmdOpenTarget>
      ...
    </Items>
  </CommandLineSpecificOptions>
  <FieldMappings>
    <Items>
      <FieldMapping>
        <Source>
          <FieldName>Department</FieldName>
        </Source>
        <Target>
          <FieldName>DEPARTMENT</FieldName>
        </Target>
      </FieldMapping>
      <FieldMapping>
        <Source>
          <FieldName>ActualityDate</FieldName>
        </Source>
        <Target>
          <FieldName>ACTUALITY_DATE</FieldName>
        </Target>
      </FieldMapping>
      <...>
    </Items>
  </FieldMappings>
</ExportSettings>