[AutoImport]

The Auto Import section was initially designed to be used exclusively by MONIMP (short for monitor import) as a windows command line utility to import over night from the Monitor Business Machines system. See How to use MONIMP.

It was later extended to include other PMA systems. See How to use MONIMP to import automatically overnight from accounting systems.

AutoImportServiceComputerName

Used by: MonimpSV.

Version 2.11.4 onwards

Max length: 30 characters

Example:

AutoImportServiceComputerName= PC7

AutoImportServiceComputerName is the name of the computer on which the the MonTel Auto import service (MonimpSV) is running.

This field overrides DefaultServiceComputerName.

AutoImportServiceLoginName

Used by: MonimpSV.

Version 2.11.4 onwards

Max length: 30 characters

Example:

AutoImportServiceLoginName = FS1\MonTel

AutoImportServiceLoginName is the Domain\login name setting for the network account user name for MonTel Auto import service (MonimpSV) on a network. Since this account needs to be a network account to access files on the network it requires the domain name as well. You cannot (or should not) use the local system account for MonTel services.

This field overrides DefaultServiceLoginName.

AutoImportPipeTextOut

Used by: MonImpSv.

Version 2.11.8 onwards.

Example:

AutoImportPipeTextOut = 0

When AutoImportPipeTextOut = 1 the MonTel Server Console or Service will send the screen information by a "named pipe" to the relevant MonTel Service Manager program (MTAdmin) which will allow the MonTel supervisor to be able to monitor the service from their local PC. This is the over rides the general default setting DefaultPipeTextOut.

AutoImportPipeInstances

Used by: MonImpSv.

Version 2.11.8 onwards.

Example:

AutoImportPipeInstances = 5

By default AutoImportPipeInstances is set to 5, which is the maximum value. This can be reduced to limit the number of external connections to a Server, or to reduce network traffic. If it is set to 0 then the Text out pipe is turned off.

A pipe instance is one channel between a MonTel service or console application and the Service manager, which is acting as a graphical user interface for the application. One channel or pipe is used for each open Service manager.

The text pipe is screen information sent by a "named pipe" to the relevant MonTel Service manager (MTAdmin). This is the over rides the general default setting DefaultPipeInstances.

AutoImportRecoverWaitTimes

Used by: LogSvc (forMonImpSV).

Version 2.11.7 onwards.

Example:

AutoImportRecoverWaitTimes = 5,10,82

This settings is a comma delimited list of time in seconds that LogSvc.exe should pause before restarting a service. LogSvc.exe is passed the failure count by the service control system in Windows and chooses the pause in the list in order of the failure count, with the last time being repeated for subsequent failures.

To prevent LogSvc.exe from restarting the service, set the value to a negative number.

The default is the value in DefaultServiceRecoverWaitTimes. This setting over rides the general default setting DefaultServiceRecoverWaitTimes. By default DefaultServiceRecoverWaitTimes is set to 5, 82.

AutoImportIterateThroughGroups

Used by: Monimp??

Version 2.10.0 Onwards (however, inactivated in EdIni)

2.11.1 onwards: Used by MonimpSv.exe

Value: 0 or 1

Example:

AutoImportIterateThroughGroups = 0

If AutoImportIterateThroughGroups is set to 1 then each time MonimpSv it will check the groups settings to find additional ClientDBs and Auto Import information to use.

These options are designed to use in a situation where there might be multiple clients sharing a PABX.

AutoImportTime

Used by: MonimpSv.exe

2.11.1 onwards: Used by MonimpSv.exe

Example:

AutoImportTime = "23:45:00"

The specific time of day for a Auto Import (using the Auto Import Service). This is used instead of AutoImportFrequency, and allows you to specify a specific time of day at which time MonimpSv should un-pause itself and import all relevant files. AutoImportRoundFrequency is ignored.

This item will be ignored if AutoImportFrequency has a value set (above 0).

2.10.18 This setting is included in EdIni32 for 2.10.x but is unused. Its inclusion allows sites testing components of Version 2.11.x to maintain the same PABX.INI file settings.

AutoImportFrequency

Used by: MonimpSv.exe

Value range: 0 to 86400

2.11.1 onwards: Used by MonimpSv.exe

Example:

AutoImportFrequency = 3660

The number of seconds between Auto Imports (using the Auto Import Service). This is used instead of AutoImportTime, and allows you to specify the frequency at which should un-pause itself and import the relevant files. AutoImportRoundFrequency will round this time to the start of nearest whole period.

A value in this item will over-ride any supplied value in the AutoImportTime item.

A value of 0 will cause MonimpSv.exe not to pause at all. A value of 1 is the equivalent of not pausing, though this would be unnecessarily expensive as an ODBC connection will be made across the network each second.

2.10.18 This setting is included in EdIni32 for 2.10.x but is unused. Its inclusion allows sites testing components of Version 2.11.x to maintain the same PABX.INI file settings.

AutoImportRoundFrequency

Used by: MonimpSv.exe

2.11.1 onwards: Used by MonimpSv.exe

Example:

AutoImportRoundFrequency = 1

By default this value is 0. When set (that is 1) and AutoImportFrequency is greater than 0, it will take the value in AutoImportFrequency, and modify it so that the next export actually the start of the next rounded down period if that period is and hour or a day. For example if AutoImportFrequency=3600 (3600 seconds in an hour), then AutoImportRoundFrequency=1 will cause the next Auto Import to be at the top of the hour (e.g. 03:00:00 AM rather than 03:17:23 AM. Likewise if AutoImportFrequency greater than or equal to 86400 then the Auto import will take place at midnight.

AutoImportRoundFrequency will not round down to periods greater than a day.

2.10.18 This setting is included in EdIni32 for 2.10.x but is not used. It was included to maintain compatibility with the new 2.11.x INI files while testing.

AutoImportSecsAfterFileChange

Used by: MonimpSv.exe

2.12.0 onwards: Used by MonimpSv.exe (This setting was present in late 2.11 versions by not documented).

Example:

AutoImportSecsAfterFileChange= 120

By default this value is 0. When set and AutoImportSecsAfterFileChange is greater than 0, it will wait that number of seconds after a file (in AutoImportFilePathName or similar) has changed, and then commence an import (or resume from the paused state).

This value should be greater than the worst case for creating the file that is to be imported. For example if the PMA system takes two minutes in the worst case to create the data that needs to be imported by MonImpSv, then you might want to wait, say, 480 seconds to allow the file to complete (in this case twice the time or 4 minutes).

This is an alternative import method to AuotImportFrequency.

This setting will not work with direct SQL imports (only with file base imports).

AutoImportReplaceEntry

Used by: Client (specifically Monimp32.exe)

Example:

AutoImportReplaceEntry = 0

0 or 1

Set to one it will overwrite exiting records (changing address and so on) except the Notes field.

If ActivateClientDBOnlyWhenUsing is not set in the [ClientDB] section then MONIMP32 will need to have exclusive access to the Master Client database to be able to overwrite or replace. If other users are still using MonTel MONIMP32 will report an error:

"Unable to open the Master Client Data Base Exclusively. To replace or overwrite files requires that no other users have MonTel open."

AutoImportMarkAllTerminated

Used by: Client (specifically Monimp32.exe)

Example:

AutoImportMarkAllTerminated = 1

Causes all records in Client, Matters Disbursements (v2.8 Patch 1 onwards) and Employees and Activities (for v2.9 onwards ) to be marked as terminated before the import. Records found, and imported as un terminated, are then re-marked as un-terminated, thus effectively deleting all other records (in the tables listed above).

For version 2.9.0 Pre-release vii onwards.

Since this makes no sense unless it can replace an entry marked as terminated AutoImportReplaceEntry is read as 1 if this value is set.

For version 2.10.14 Pre-release onwards.

Where AutoImportMarkAllTerminated was set to one in previous versions it would mark all records as terminated, and then import the current list progressively marking them as un-terminated, thereby leaving just the old or deleted records as terminated. This worked well for overnight imports, however with the SQL data engine imports are now being done during the day. As a consequence records will be marked as deleted for the time it takes to reimport them, which make be several minutes.

To prevent this issue the AutoImportMarkAllTerminated now flags but does not terminate all records. The flags are unset if the record is imported. Then the remaining flagged records are marked as terminated.

AutoImportAllowDestructiveIniUpdate

Topic creation date: 2008-08-09

Used by: Monimpsv.

Version 2.12.1 onwards

0 or 1

Example:

AutoImportAllowDestructiveIniUpdate = 0

By default this setting is 0. This is very much a safety first setting. When set to 1, it gives Monimpsv permission to overwrite the PABX.INI file with new data if the MIF filter and the PMA.INI file settings are set accordingly. Since overwriting the PABX.INI file could potentially be disastrous you would only want to enable this setting if you had a specific purpose, such as updating the current MonTel users from the Monitor Business MAchines system using the DMON4.MIF filter. See ImportDestructiveUpdateOfUsersInIniFile in the PMA.INI file settings.

AutoImportEmployeeFilePathName

Topic creation date: 2009-04-22

Used by: MonimpSV, ParsIn.

Version 2.12.20 onwards

Max length: 128 characters

Example:

AutoImportEmpolyeeFilePathName = "//netwizdn/apps/montel/data_in/employee.csv"

AutoImportEmpolyeeFilePathName is used to specify the path and file name, or other details such as the DSN for importing employee or user details from an external system into MonTel. The path must be a true name or UNC path in the format, //{server}/{share}/{path}/{file}, as this path will be used by a service which will not have access to drive letter, unless the path happens to reside on the local computers C drive.

To import users from Active Directory (using LDAP) specify AutoImportEmpolyeeFilePathName ="LDAP", and set the ImportReportFormat in the [import] section of the PMA.INI file to the relevant value for LDAP imports.

This item is a direct replacement for AutoImportFilePathName1 or AutoImportFilePathName when AutoTypeOfImportRecord = 1 in MonTel version 2.12.19 and before.

AutoImportPrimaryLinkFilePathName

Topic creation date: 2009-04-22

Used by: MonimpSV, ParsIn.

Version 2.12.20 onwards

Max length: 128 characters

Example:

AutoImportPrimaryLinkFilePathName = "//netwizdn/apps/montel/data_in/client.csv"

AutoImportPrimaryLinkFilePathName is used to specify the path and file name, or other details such as the DSN for importing client or matter details from an external system into MonTel. The path must be a true name or UNC path in the format, //{server}/{share}/{path}/{file}, as this path will be used by a service which will not have access to drive letter, unless the path happens to reside on the local computers C drive.

The use of Client or Matters, will depend on a number of factors. Generally this will depend on the the Primary Link or the charge item. Typically for an accounting firm this would be a client code. For a legal firm this would be a Matter or Job code. Where a secondary link is required and this is present in a different table of file, you may need to specify AutoImportSecondaryLinkFilePathName. In some systems both clients and matters will be imported from the same file. In such a case the AutoImportPrimaryLinkFilePathName is used rather than the AutoImportSecondaryLinkFilePathName, and the translation is dealt with internally.

In some case even though the PrimaryLink is to a client, the matter field may be populated and vice versa. How this is done is determined by the filter and the type of PMA system.

This item is a direct replacement for AutoImportFilePathName2 or AutoImportFilePathName when AutoTypeOfImportRecord = 2 in MonTel version 2.12.19 and before.

AutoImportActivityFilePathName

Topic creation date: 2009-04-22

Used by: MonimpSV, ParsIn.

Version 2.12.20 onwards

Max length: 128 characters

Example:

AutoImportActivityFilePathName = "//netwizdn/apps/montel/data_in/time_codes.csv"

AutoImportActivityFilePathName is used to specify the path and file name, or other details such as the DSN for importing Activity details from an external system into MonTel. The path must be a true name or UNC path in the format, //{server}/{share}/{path}/{file}, as this path will be used by a service which will not have access to drive letter, unless the path happens to reside on the local computers C drive.

Often, this setting is not used, and disbursements must be set manually or in the ClientDB.INI file. For charging purposes activities are not used. This import is provided to assist with note taking, and for future expansion in the even MonTel is used for time sheet purposes.

This item is a direct replacement for AutoImportFilePathName3 or AutoImportFilePathName when AutoTypeOfImportRecord = 3 in MonTel version 2.12.19 and before.

AutoImportDisbursmentFilePathName

Topic creation date: 2009-04-22

Used by: MonimpSV, ParsIn.

Version 2.12.20 onwards

Max length: 128 characters

Example:

AutoImportDisbursmentFilePathName = "//netwizdn/apps/montel/data_in/charge_codes.csv"

AutoImportDisbursmentFilePathName is used to specify the path and file name, or other details such as the DSN for importing disbursement or charge code details from an external system into MonTel. The path must be a true name or UNC path in the format, //{server}/{share}/{path}/{file}, as this path will be used by a service which will not have access to drive letter, unless the path happens to reside on the local computers C drive.

Often, this setting is not used, and disbursements must be set manually or in the ClientDB.INI file.

This item is a direct replacement for AutoImportFilePathName4 or AutoImportFilePathName when AutoTypeOfImportRecord = 4 in MonTel version 2.12.19 and before.

AutoImportSecondaryLinkFilePathName

Topic creation date: 2009-04-22

Used by: MonimpSV, ParsIn.

Version 2.12.20 onwards

Max length: 128 characters

Example:

AutoImportSecondaryLinkFilePathName = "//netwizdn/apps/montel/data_in/matter.csv"

AutoImportSecondaryLinkFilePathName is used to specify the path and file name, or other details such as the DSN for importing secondary or linked client or matter details from an external system into MonTel. The path must be a true name or UNC path in the format, //{server}/{share}/{path}/{file}, as this path will be used by a service which will not have access to drive letter, unless the path happens to reside on the local computers C drive.

This field is often not used. Even when a secondary link (client needing a matter or matter or job code referring to a client) the AutoImportPrimaryLinkFilePathName setting may contain all the required information. Weather this file is needed is determined by the filter and the type of PMA system.

This item is a direct replacement for AutoImportFilePathName5 or AutoImportFilePathName when AutoTypeOfImportRecord = 5 in MonTel version 2.12.19 and before.

AutoTypeOfImportRecord

Used by: Monimp32.exe, MonimpSV and Import32.exe

Up to Version 2.12.19

Value: 0-5

Example:

AutoTypeOfImportRecord = 1

Corresponds to the number the type of import matching the table below, that describes the import type for AutoImportFilePathName.

Generally this value would be AutoTypeOfImportRecord = 2 as this covers the primary client or matter table.

Special Note. This entry set up a default for MONIMP32.EXE which can be overridden by the command line for MONIMP32. This is for an overnight import of just one file. For multiple files see the next entries down.

There are five potential types in use for any particular system. When applicable the types are generally follow the table below.

Type	Value
Employee	1
Client (or Matters)	2
Activity	3
Disbursement	4
Matter (or Client)	5

However, each filter may treat or translates the types into something slightly different. For example the value 2 may point to a file that is used for both clients and matters, and the way it is determined depends on MatterClientRelationship setting from the PMA.INI file.

The use of Client or Matters (2 or 5), will depend on a number of factors. Firstly, the value of 2 is used for the Primary Link or the charge item. Typically for an accounting firm this would be a client code. For a legal firm this would be a Matter or Job code. Where a secondary link is required and this is present in a different table of file, 5 may be specified.

For more detail look at the detail for the specified '.mif' import filter file.

AutoImportFilePathName

Used by: Monimp32.exe, MonimpSV and Import32.exe

Max length: 140 characters

Example:

AutoImportFilePathName = "c:\pabxsd\matters.exp"

File and path name of the import text file. The type of import is determined by AutoTypeOfImportRecord. Use this setting only when specifying the AutoTypeOfImportRecord. This setting is likely to be deprecated in the future

For multiple file import, don't use the this and AutoTypeOfImportRecord (leave them blank). Rather, use the fields that have a digit appended to the key to match the type of import record. These are the entries AutoImportFilePathName1 through AutoImportFilePathName5 below.

Special Note. This entry set up a default for MONIMP32.EXE which can be overridden by the command line for MONIMP32. This is for an overnight import of just one file. For multiple files see the next entries down.

For MonimpSV (2.11.3 onwards) the path must be a true name or UNC path in the format, //{server}/{share}/{path}/{file}.

AutoImportFilePathName1

Used by: Monimp32.exe, MonimpSV and Import32.exe

Up to Version 2.12.19

Max length: 140 characters

Example:

AutoImportFilePathName1 = "c:\pabxsd\employee.csv"

AutoImportFilePathName1 is used to specify the path and file name of a type 1 import when more than one type of file is to be imported form another system. Typically a type 1 import is for an employee list. See also AutoTypeOfImportRecord.

For MonimpSV (2.11.3 onwards) the path must be a true name or UNC path in the format, //{server}/{share}/{path}/{file}.

For MonimpSV (2.11.20 onwards) to import users from Active Directory (using LDAP) specify AutoImportFilePathName1 ="LDAP".

AutoImportFilePathName2

Used by: Monimp32.exe, MonimpSV and Import32.exe

Up to Version 2.12.19

Max length: 140 characters

Example:

AutoImportFilePathName2 = "c:\pabxsd\matters.exp"

AutoImportFilePathName2 is used to specify the path and file name of a type 2 import when more than one type of file is to be imported form another system. Typically a type 2 import is for an client list. See also AutoTypeOfImportRecord.

For MonimpSV (2.11.3 onwards) the path must be a true name or UNC path in the format, //{server}/{share}/{path}/{file}.

AutoImportFilePathName3

Used by: Monimp32.exe, MonimpSV and Import32.exe

Up to Version 2.12.19

Max length: 140 characters

Example:

AutoImportFilePathName3 =

AutoImportFilePathName3 is used to specify the path and file name of a type 3 import when more than one type of file is to be imported form another system. Typically a type 3 import is for an activity list. See also AutoTypeOfImportRecord.

For MonimpSV (2.11.3 onwards) the path must be a true name or UNC path in the format, //{server}/{share}/{path}/{file}.

AutoImportFilePathName4

Used by: Monimp32.exe, MonimpSV and Import32.exe

Up to Version 2.12.19

Max length: 140 characters

Example:

AutoImportFilePathName4 =

AutoImportFilePathName4 is used to specify the path and file name of a type 4 import when more than one type of file is to be imported form another system. Typically a type 4import is for an disbursment list. See also AutoTypeOfImportRecord.

For MonimpSV (2.11.3 onwards) the path must be a true name or UNC path in the format, //{server}/{share}/{path}/{file}.

AutoImportFilePathName5

Used by: Monimp32.exe, MonimpSV and Import32.exe

Up to Version 2.12.19

Max length: 140 characters

Example:

AutoImportFilePathName5 =

AutoImportFilePathName5 is used to specify the path and file name of a type 5 import when more than one type of file is to be imported form another system. Typically a type 5 import is for a secondary code, for example a matter list if clients were imported for AutoImportFilePathName2. See also AutoTypeOfImportRecord.

For MonimpSV (2.11.3 onwards) the path must be a true name or UNC path in the format, //{server}/{share}/{path}/{file}.

DontMakeImportNotes

Used by: Monimp32.exe, MonimpSV and Import32.exe

Example:

DontMakeImportNotes = 1

Default is 0, which means that in the note fields of Client, Contact and Matter will be updated with the date, time and the type of import. When set to one notes will not be added reducing the data space overhead, since if imports are happening on a regular basis (say overnight) the extra space overhead will cause the Master Client Database to grow over time. In addition, if updates are made straight a "Jet" Master Client Database, the database will experience significant growth from the overhead of recompiled SQL queries of updates of the note fields. This can be reduced by setting AutoImportThroughLocalDB = 1.

For version 2.9.0 Pre-release xxxxiv onwards.