Difference between revisions of "OS4X Enterprise partner migration"
(New page: OS4X Enterprise offers various import possibilities of hierarchical data of partner information. If none of the offeres solutions fits your needs, please contact us in order to search for ...) |
|||
| Line 11: | Line 11: | ||
#Import "departments and recipients" CSV | #Import "departments and recipients" CSV | ||
The second step is based on the first step, so it would make no sense to switch the order of import. | The second step is based on the first step, so it would make no sense to switch the order of import. | ||
| + | |||
| + | == EurexC == | ||
| + | The import of EurexC based systems can be divided in two supported versions: | ||
| + | *Versions of EurexC CAD base which have the partner configuration in a file named "<code>xx020.d</code>" | ||
| + | *Versions of EurexC CAD base which have the partner configuration in a file named "<code>xx030.d</code>" | ||
| + | |||
| + | == WinElke == | ||
| + | WinElke systems which are based on MS Access databases can be imported on a limited amount of platforms which support the binaries for the required tools. Just upload the MS Access file if the button is enabled. | ||
| + | |||
| + | == SWAN 3.x == | ||
| + | The partner databae schema must exist in the same database which OS4X is working on. If the underlying tables exist, but the button is disabled, please contact us in order to verify your (possibly inconsistent) data. | ||
| + | |||
| + | == Generic CSV == | ||
| + | Via the Daxware import possibility, you can generate CSV files with a given format in order to import your partner data. The format of the files must follow a fix syntax. | ||
| + | |||
| + | The CSV for companies and locations (in one file) must contain exactly this following header line as the first line to be contained in the CSV file: | ||
| + | Companyname;Street;Housenumber;PostalCode;City;Country;Phonenumber;Fax;SSID;SFID;Net;Address;Password;Characterset;Fileformat;Recordsize; | ||
| + | |||
| + | The second file for departments and recipients must contain exactly this following header line as the first line to be contained in the CSV file: | ||
| + | Companyname;Companylocation;Lastname;Firstname;Phonenumber;Mobilenumber;Faxnumber;eMail;Department;Password;Userrole; | ||
| + | |||
| + | The references between the two files are the names of the company (1. "Companyname" = 2. "Companyname" )and the location name 1. "City" = 2. "Companylocation"). | ||
Revision as of 10:38, 26 February 2013
OS4X Enterprise offers various import possibilities of hierarchical data of partner information. If none of the offeres solutions fits your needs, please contact us in order to search for a valid solution, we will help you out.
Doing
Most partner import processes are executed via the administrative web interface. Locate the menu entry point "Programs" -> "Partner import":
Daxware import
Daxware 2002 installations can export their partner information in CSV format, so the two steps have to be executed in the following order:
- Import "partner companies and locations" CSV
- Import "departments and recipients" CSV
The second step is based on the first step, so it would make no sense to switch the order of import.
EurexC
The import of EurexC based systems can be divided in two supported versions:
- Versions of EurexC CAD base which have the partner configuration in a file named "
xx020.d" - Versions of EurexC CAD base which have the partner configuration in a file named "
xx030.d"
WinElke
WinElke systems which are based on MS Access databases can be imported on a limited amount of platforms which support the binaries for the required tools. Just upload the MS Access file if the button is enabled.
SWAN 3.x
The partner databae schema must exist in the same database which OS4X is working on. If the underlying tables exist, but the button is disabled, please contact us in order to verify your (possibly inconsistent) data.
Generic CSV
Via the Daxware import possibility, you can generate CSV files with a given format in order to import your partner data. The format of the files must follow a fix syntax.
The CSV for companies and locations (in one file) must contain exactly this following header line as the first line to be contained in the CSV file:
Companyname;Street;Housenumber;PostalCode;City;Country;Phonenumber;Fax;SSID;SFID;Net;Address;Password;Characterset;Fileformat;Recordsize;
The second file for departments and recipients must contain exactly this following header line as the first line to be contained in the CSV file:
Companyname;Companylocation;Lastname;Firstname;Phonenumber;Mobilenumber;Faxnumber;eMail;Department;Password;Userrole;
The references between the two files are the names of the company (1. "Companyname" = 2. "Companyname" )and the location name 1. "City" = 2. "Companylocation").