...

The import process require a configuration of folders, filenames, transformers, handlers, logging etc,. Once this is setup the service is working automatically to handle new data.

Data flow and process:

1. A new file is generated on a predefined disk area by an external system

2. The service supervises the disk area and detects the new file, the file name is compared to a name pattern to determine if the file is handled and how it is handled

3. The import handler is called to transform the file to an internal format suitable for upload

4. The items loaded to the importer is passed to the uploader

5. The uploader handler calls a remote server Api, passing a chunk of items

6. The remote Api will handle the data and store it to the server, the REST call indicates what interface is called and type of the data to store

Installation

1. Run the installer.

2. Possibly register the service, see Windows Service installer finishes correctly but service is missing.

3. Ensure Signifikant Service is run under “Local System” or an account which has access to SQL Server.

Configuration

Imported data

...

Sample configuration

<?xml version="1.0" encoding="utf-8"?>
<CustomFolderConfiguration xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
	<Enabled>true</Enabled>
	<!-- In case SaveItem is true, importer service will save imports directly to the database. In this case importer service will 
	need to know where to find the server.config file since it may be either in AppData or in Program data depending on if importer 
	service is installed on Manager Server or on Web Server. -->
	<ServerConfigPath>C:\ProgramData\Signifikant\Assert\server.config</ServerConfigPath>
	<!-- Log files placed here. -->
	<LogFolder>C:\Signifikant\Log\ImportLog</LogFolder>
	<!-- File watcher will be recreated every x hrs. Default is 0 which means no recreation. Setting available from version 5.1.7 and later. -->
	<SuperviseHours>48</SuperviseHours>
	
	<Settings>
		<CustomFolderSettings ImporterId="Parts">
			<DumpUploadItems>true</DumpUploadItems>
			<FolderDescription>Part status</FolderDescription>
			<FolderEnabled>true</FolderEnabled>
			<FolderFilter>Parts*.xml</FolderFilter>
			<FolderPath>C:\Signifikant\Import_service</FolderPath>
			<BackupFolder>C:\Signifikant\Import_service_backup</BackupFolder>
			<FolderIncludeSub>false</FolderIncludeSub>
			<MoveToBackup>true</MoveToBackup>
			<SaveItems>true</SaveItems>
			<XlsSheet/>
			<SsxSheet>signifikant_parts.xsl</SsxSheet>
			<UploadItems>true</UploadItems>
			<UploadServer>http://localhost/AssertWeb/</UploadServer>
			<UploaderId>Parts</UploaderId>
			<UploadSiteId>Alo</UploadSiteId>
			<UploadLogin>false</UploadLogin>
			<UploadUsername>uploader</UploadUsername>
			<UploadPassword>uploader</UploadPassword>
			<Options>
				<Option key="PurgeAfter" value="true"/>
			</Options>
		</CustomFolderSettings>
		<CustomFolderSettings ImporterId="PartsPrice">
			<DumpUploadItems>true</DumpUploadItems>
			<FolderDescription>Part price</FolderDescription>
			<FolderEnabled>true</FolderEnabled>
			<FolderFilter>PartsPrice*.xml</FolderFilter>
			<FolderPath>C:\Signifikant\Import_service</FolderPath>
			<BackupFolder>C:\Signifikant\Import_service_backup</BackupFolder>
			<FolderIncludeSub>false</FolderIncludeSub>
			<MoveToBackup>true</MoveToBackup>
			<SaveItems>true</SaveItems>
			<XlsSheet/>
			<SsxSheet>signifikant_price.xsl</SsxSheet>
			<UploadItems>true</UploadItems>
			<UploadServer>http://localhost/AssertWeb/</UploadServer>
			<UploaderId>PartsPrice</UploaderId>
			<UploadSiteId>Alo</UploadSiteId>
			<UploadLogin>false</UploadLogin>
			<UploadUsername>uploader</UploadUsername>
			<UploadPassword>uploader</UploadPassword>
			<Options>
				<Option key="PurgeAfter" value="true"/>
			</Options>
		</CustomFolderSettings>
		<CustomFolderSettings ImporterId="PartsBalance">
			<FolderEnabled>true</FolderEnabled>
			<FolderDescription>Part availability</FolderDescription>
			<FolderFilter>PartsBalance*.xml</FolderFilter>
			<FolderPath>C:\Signifikant\Import_service</FolderPath>
			<BackupFolder>C:\Signifikant\Import_service_backup</BackupFolder>
			<FolderIncludeSub>false</FolderIncludeSub>
			<MoveToBackup>true</MoveToBackup>
			<SaveItems>true</SaveItems>
			<SsxSheet>signifikant_avaibility.xsl</SsxSheet>
			<UploadItems>true</UploadItems>
			<UploadServer>http://localhost/AssertWeb/</UploadServer>
			<UploaderId>PartsBalance</UploaderId>
			<UploadSiteId>Alo</UploadSiteId>
			<UploadLogin>false</UploadLogin>
			<UploadUsername>uploader</UploadUsername>
			<UploadPassword>uploader</UploadPassword>
			<Options>
				<Option key="PurgeAfter" value="true"/>
			</Options>
		</CustomFolderSettings>
		<CustomFolderSettings ImporterId="Organizations">
			<FolderEnabled>true</FolderEnabled>
			<FolderDescription>Organization import</FolderDescription>
			<FolderFilter>Organisations*.xml</FolderFilter>
			<FolderPath>C:\Signifikant\Import_service</FolderPath>
			<BackupFolder>C:\Signifikant\Import_service_backup</BackupFolder>
			<FolderIncludeSub>false</FolderIncludeSub>
			<MoveToBackup>true</MoveToBackup>
			<SaveItems>true</SaveItems>
			<SsxSheet>signifikant_organization.xsl</SsxSheet>
			<UploadItems>true</UploadItems>
			<UploadServer>http://localhost/AssertWeb/</UploadServer>
			<UploaderId>Organizations</UploaderId>
			<UploadSiteId>Alo</UploadSiteId>
			<UploadLogin>false</UploadLogin>
			<UploadUsername>uploader</UploadUsername>
			<UploadPassword>uploader</UploadPassword>
			<Options>
				<Option key="PurgeAfter" value="true"/>
			</Options>
		</CustomFolderSettings>
		<CustomFolderSettings ImporterId="Users">
			<FolderEnabled>true</FolderEnabled>
			<FolderDescription>User Import</FolderDescription>
			<FolderFilter>Users*.xml</FolderFilter>
			<FolderPath>C:\Signifikant\Import_service</FolderPath>
			<BackupFolder>C:\Signifikant\Import_service_backup</BackupFolder>
			<FolderIncludeSub>false</FolderIncludeSub>
			<MoveToBackup>true</MoveToBackup>
			<SaveItems>true</SaveItems>
			<SsxSheet>signifikant_user.xsl</SsxSheet>
			<UploadItems>true</UploadItems>
			<UploadServer>http://localhost/AssertWeb/</UploadServer>
			<UploaderId>Users</UploaderId>
			<UploadSiteId>Alo</UploadSiteId>
			<UploadLogin>false</UploadLogin>
			<UploadUsername>uploader</UploadUsername>
			<UploadPassword>uploader</UploadPassword>
			<Options>
				<Option key="PurgeAfter" value="false"/>
			</Options>
		</CustomFolderSettings>
	</Settings>
</CustomFolderConfiguration>

Desrciption of tags

...

Tags

...

Description

...

Options

...

ServerConfigPath

...

Path to the server.config file where configuration is kept for the editor- or web-server. Important is the Notification settings, and the integration to Monitoring dashboard.

...

For an editor server: C:\ProgramData\Signifikant\Assert\server.config.

For a web server: C:\inetpub\wwwroot\AssertWeb\App_Data

...

FolderEnabled

...

If configuration is active or not.

...

true/false

...

FolderDescription

...

Description.

...

text

...

FolderFilter

...

Regex used on the files that appear in the folder. Only files matching the regex will be handled, e.g. Part_price*.xml.

...

FolderPath

...

Folder path to monitor for new files.

...

FolderIncludeSub

...

If sub folders are to be scanned for imports.

...

true/false

...

MaxIdleDays

...

Time limit when it is considered an error if no new import files arrive, see below.

...

integer

...

MaxIdleHours

...

Time limit when it is considered an error if no new import files arrive, see below.

...

integer

...

MoveToBackup

...

If file is to be moved to backup folder.

...

true/false

...

BackupFolder

...

After an import or upload is completed, move file to this folder.

...

SaveItems

...

If file content is to be saved on database on same server as importer service runs on.

...

true/false

...

SiteId

...

Site name when importing into Manager site.

...

Site name

...

UploadItem

...

If file content is to be uploaded to web server site.

...

true/false

...

UploadSiteId

...

Site name when uploading into web viewer site.

...

Site name

...

UploadServer

...

Url for the web server e.g https://www.domain.com/AssertWeb/

...

UploaderId

...

Type of upload, see table above.

...

See table above

...

UploadLogin

...

If login required to upload items to webserver.

...

true/false

...

UploadUsername

...

	<CustomFolderSettings ImporterId="Invoice">
          <FolderEnabled>true</FolderEnabled>
          <FolderDescription>Initial data place holder and template (Invoices for Dometic)</FolderDescription>
          <FolderFilter>Invoice*.xml</FolderFilter>
          <FolderPath>C:\Signifikant\Import_service</FolderPath>
          <DeleteAfterImport>true</DeleteAfterImport>
          <FolderIncludeSub>false</FolderIncludeSub>
          <SaveItems>true</SaveItems>
          <XlsSheet>signifikant_invoice.xsl</XlsSheet>
          <SsxSheet />
          <UploadItems>true</UploadItems>
          <UploaderId>Invoice</UploaderId>
          <UploadServer>http://localhost/AssertWeb/</UploadServer>
          <UploadUsername>uploader</UploadUsername>
          <UploadPassword>uploader</UploadPassword>
          <UploadLogin>false</UploadLogin>
          <Options>
            <Option key="PurgeAfter" value="false"/>
          </Options>
        </CustomFolderSettings>
	</Settings>
</CustomFolderConfiguration>

Desrciption of tags

Options tag has a set of keys.

...

Key

...

Value

...

Description

...

Options

...

PurgeAfter

...

bool

...

After last call with all uploaded part numbers, a valid number list with all valid part numbers are uploaded. All parts in the price list or warehouse lists which not in the valid numbers list removed from that price list or warehouse list. That way removed prices/warehouse stock will get deleted.

Use this method if full price lists or warehouse lists are sent.

Customization

Custom style sheet may be used to transform input format. Use tag <SsxSheet> to define a custom xsl.

Handlers for import or upload to remote server may be added in a customize module. By referring the custom handler in service configuration, any customer use case regarding automated file import, can be implemented. Custom modules require programming.

Permissions

The remote server may require permissions to access the upload Api interface. In that case we use basic authentication with a username/password to secure the function.

In this case the service need to declare login parameters for an upload handler, in the service configuration.

Logging

Configuration declares folders for logging, where each handler appends text to one file per day. Example of a log file name: UploadService_20200528_PartsPrice.log, indicating price information was uploaded.

The service also logs to an application log file, normally found at: C:\ProgramData\Signifikant\Assert\ImportService.log

Mail and event notification

Setting is available in 5.1.1 and later. Notification is made by mail, by monitoring event or both.

Notification by mail

Time limit when it is considered an error if no new import files arrive. If no import files arrives within the defined number of hours and days, a notification is created. The notification is defined in server.config.

<Notification>
	<Type>Service</Type>
	<MailEnabled>true</MailEnabled>
	<MailRecipient>support@company.com</MailRecipient>
	<MailSender>noreply@company.com</MailSender>
	<MailAtSuccess>false</MailAtSuccess>
	<MailAtFailure>true</MailAtFailure>
</Notification>

If none of MaxIdleHours and MaxIdleDays are defined, no monitoring will be turned on.

Notification by event generation to monitoring dashboard

To send import events to the monitoring dashboard, it uses a configuration file monitoring-service-client.json. The file is located in the same folder as the file defined by the ServerConfigPath element. Ensure that the file is in the same folder as the active server.config file. Should the file be missing. an empty file is generated, as a template for configuration. It has the enabled attribute defined to false to disable event generation initially.

Example of file monitoring-service-client.json, apiKey is received from Signifikant, externalId and customer may be used to identify events later.

{
    "enabled": true,
    "url": "https://development.signifikant.se/monitoringserviceapi/",
    "apiKey": "*",
    "defaults": {
        "externalId": "id",
        "customer": "name"
    },
    "apiKeyHeaderName": "api-key",
    "sendUrl": "api/event"
}

Custom Xsl for uploads

Overview

Xsl files transform customer exported files in one Xml format to a format that the import/upload engine handles. File names are entered in the configuration file and the file is located in common or custom program data folders.

Prices

Input format

Standard input format:

<?xml version="1.0" encoding="UTF-8"?>
<Export>
	<Metadata>
		<export-type>SignifikantSimplifiedXml</export-type>
		<export-time>2018-02-09T13:54:43.074+01:00</export-time>
		<version>1.0</version>
	</Metadata>
	<PartsPrices>
		<PartPrice>
			<Price>125</Price>
			<PartPriceGroupName>MAGFR01</PartPriceGroupName>
			<CurrencyCode>SEK</CurrencyCode>
			<PartNumber>60045910</PartNumber>
		</PartPrice>
	</PartsPrices>
</Export>

Output format

The price conversion Xsl file generates output records, one for each parts price for a price list.

<PartPrice number="12345" price="1.25" currency="SEK" price-list="PRICELIST"/>

If a part has a price list which does not exist, that price list will be created and made available. It will not be a default price list.

Availability

Input format

Standard input format:

<?xml version="1.0" encoding="UTF-8"?>
<Export>
	<Metadata>
		<export-type>SignifikantSimplifiedXml</export-type>
		<export-time>2018-02-09T13:54:43.074+01:00</export-time>
		<version>1.0</version>
	</Metadata>
	<PartsBalances>
		<PartBalance>
			<PartNumber>60045910</PartNumber>	
			<WarehouseName>MAGFR01</WarehouseName>
			<Balance>112</Balance>
		</PartBalance>
	</PartsBalances>
</Export>

Output format

The availability conversion Xsl file generates output records, one for each parts balance for a warehouse. The total of balance + supply-balance is loaded to the database - 137 in the example below.

<PartBalance number="12345" total-balance="25" warehouse="STORE"/>

If a part has a warehouse which does not exist, that warehouse will be created and made available. It will not be a default warehouse.

Part status

Input format

...

Options tag has a set of keys.

Customization

Custom style sheet may be used to transform input format. Use tag <SsxSheet> to define a custom xsl.

Handlers for import or upload to remote server may be added in a customize module. By referring the custom handler in service configuration, any customer use case regarding automated file import, can be implemented. Custom modules require programming.

Permissions

The remote server may require permissions to access the upload Api interface. In that case we use basic authentication with a username/password to secure the function.

In this case the service need to declare login parameters for an upload handler, in the service configuration.

Logging

Configuration declares folders for logging, where each handler appends text to one file per day. Example of a log file name: UploadService_20200528_PartsPrice.log, indicating price information was uploaded.

The service also logs to an application log file, normally found at: C:\ProgramData\Signifikant\Assert\ImportService.log

Mail and event notification

Setting is available in 5.1.1 and later. Notification is made by mail, by monitoring event or both.

Notification by mail

Time limit when it is considered an error if no new import files arrive. If no import files arrives within the defined number of hours and days, a notification is created. The notification is defined in server.config.

<Notification>
	<Type>Service</Type>
	<MailEnabled>true</MailEnabled>
	<MailRecipient>support@company.com</MailRecipient>
	<MailSender>noreply@company.com</MailSender>
	<MailAtSuccess>false</MailAtSuccess>
	<MailAtFailure>true</MailAtFailure>
</Notification>

If none of MaxIdleHours and MaxIdleDays are defined, no monitoring will be turned on.

Notification by event generation to monitoring dashboard

To send import events to the monitoring dashboard, it uses a configuration file monitoring-service-client.json. The file is located in the same folder as the file defined by the ServerConfigPath element. Ensure that the file is in the same folder as the active server.config file. Should the file be missing. an empty file is generated, as a template for configuration. It has the enabled attribute defined to false to disable event generation initially.

Example of file monitoring-service-client.json, apiKey is received from Signifikant, externalId and customer may be used to identify events later.

{
    "enabled": true,
    "url": "https://development.signifikant.se/monitoringserviceapi/",
    "apiKey": "*",
    "defaults": {
        "externalId": "id",
        "customer": "name"
    },
    "apiKeyHeaderName": "api-key",
    "sendUrl": "api/event"
}

Custom Xsl for uploads

Overview

Xsl files transform customer exported files in one Xml format to a format that the import/upload engine handles. File names are entered in the configuration file and the file is located in common or custom program data folders.

Prices

Input format

Standard input format:

<?xml version="1.0" encoding="UTF-8"?>
<Export>
	<Metadata>
		<export-type>SignifikantSimplifiedXml</export-type>
		<export-time>2018-02-09T13:54:43.074+01:00</export-time>
		<version>1.0</version>
	</Metadata>
	<PartsPrices>
		<PartPrice>
			<Price>125</Price>
			<PartPriceGroupName>MAGFR01</PartPriceGroupName>
			<CurrencyCode>SEK</CurrencyCode>
			<PartNumber>60045910</PartNumber>
		</PartPrice>
	</PartsPrices>
</Export>

Output format

The price conversion Xsl file generates output records, one for each parts price for a price list.

<PartPrice number="12345" price="1.25" currency="SEK" price-list="PRICELIST"/>

If a part has a price list which does not exist, that price list will be created and made available. It will not be a default price list.

Availability

Input format

Standard input format:

<?xml version="1.0" encoding="UTF-8"?>
<Export>
	<Metadata>
		<export-type>SignifikantSimplifiedXml</export-type>
		<export-time>2018-02-09T13:54:43.074+01:00</export-time>
		<version>1.0</version>
	</Metadata>
	<PartsBalances>
		<PartBalance>
			<PartNumber>60045910</PartNumber>	
			<WarehouseName>MAGFR01</WarehouseName>
			<Balance>112</Balance>
		</PartBalance>
	</PartsBalances>
</Export>

Output format

The availability conversion Xsl file generates output records, one for each parts balance for a warehouse. The total of balance + supply-balance is loaded to the database - 137 in the example below.

<PartBalance number="12345" total-balance="25" warehouse="STORE"/>

If a part has a warehouse which does not exist, that warehouse will be created and made available. It will not be a default warehouse.

Part status

Input format

The part status import is used to set the AvailabilityCode and ReplacementCode on parts. Standard input format:

<?xml version="1.0" encoding="UTF-8"?>
<Export>
	<Metadata>
		<export-type>SignifikantSimplifiedXml</export-type>
		<export-time>2018-02-09T13:54:43.074+01:00</export-time>
		<version>1.0</version>
	</Metadata>
	<Parts>
		<Part>
				<PartNumber>60045910</PartNumber>
				<ReplacementCode>ReplaceNever</ReplacementCode>
				<AvailabilityCode>Available</AvailabilityCode>
				<PersistentIdentity>60045910</PersistentIdentity>
				<Code></Code>
		</Part>
	</Parts>
</Export>

Organizations

Input format

For the file format, refer to definition of the Signifikant import format for organization. Standard input format.

<?xml version="1.0" encoding="UTF-8"?>
<Export>
	<Metadata>
		<export-type>SignifikantSimplifiedXml</export-type>
		<export-time>2018-02-09T13:54:43.074+01:00</export-time>
		<version>1.0</version>
	</Metadata>
	<Organizations>
		<Organization>
			<PersistentIdentity>22565437447</PersistentIdentity>
			<OrganizationName>1MAN SERVICES</OrganizationName>
			<OrganizationNumber>SM09049</OrganizationNumber>
			<CustomerNumber>000069</CustomerNumber>
			<Status>New</Status>	
			<Email/>
			<PhoneNumber/>
			<FaxNumber/>
			<Note/>
			<Category>Company 2</Category>
			<Addresses>
				<Address>
					<PersistentIdentity>22565423796_1</PersistentIdentity>
					<Name>Active Systems 1</Name>
					<StreetAddress>9995 West Central Entrance</StreetAddress>
					<StreetAddress2/>
					<StreetAddress3/>
					<City>Duluth</City>
					<ZipCode>55802</ZipCode>
					<State>MN</State>
					<Country>US</Country>
					<Type>
						<Primary>false</Primary>
						<Billing>true</Billing>
						<Shipping>false</Shipping>
					</Type>
				</Address>
				<Address>
					<PersistentIdentity>22565423796_2</PersistentIdentity>
					<Name>Active Systems 2</Name>
					<StreetAddress>9995 West Central Entrance</StreetAddress>
					<StreetAddress2/>
					<StreetAddress3/>
					<City>Duluth</City>
					<ZipCode>55802</ZipCode>
					<State>MN</State>
					<Country>US</Country>
					<Type>
						<Primary>false</Primary>
						<Billing>false</Billing>
						<Shipping>true</Shipping>
					</Type>
				</Address>
				<Address>
					<PersistentIdentity>22565423796_3</PersistentIdentity>
					<Name>Active Systems 3</Name>
					<StreetAddress>9995 West Central Entrance</StreetAddress>
					<StreetAddress2/>
					<StreetAddress3/>
					<City>Duluth</City>
					<ZipCode>55802</ZipCode>
					<State>MN</State>
					<Country>US</Country>
					<Type>
						<Primary>true</Primary>
						<Billing>true</Billing>
						<Shipping>true</Shipping>
					</Type>
				</Address>
			</Addresses>
		</Organization>
	</Organizations>
</Export>

Users

Input format

Here is an example of users xml.

<?xml version="1.0" encoding="UTF-8"?>
<Export>
	<Metadata>
		<export-type>SignifikantSimplifiedXml</export-type>
		<export-time>2018-02-09T13:54:43.074+01:00</export-time>
		<version>1.0</version>
	</Metadata>
	<Parts>
		<Part>/version>
	</Metadata>
	<Users>
		<User>
			<UserName>john@mycompan.com</UserName>
			<Title>Mr</Title>
			<FirstName>John</FirstName>
				<PartNumber>60045910<<LastName>Doe</PartNumber>LastName>
				<ReplacementCode>ReplaceNever</ReplacementCode><Email>john@mycompany.com</Email>
				<AvailabilityCode>Available</AvailabilityCode><!-- Note that this is matched to organisations so user will be connected to organisation with the customer number specified. 
				<PersistentIdentity>60045910</PersistentIdentity>
				<Code></Code>
		</Part>
	</Parts>
</Export>

Organizations

Input format

For the file format, refer to definition of the Signifikant import format for organization. Standard input format.

<?xml version="1.0" encoding="UTF-8"?>
<Export>
	<Metadata>
		<export-type>SignifikantSimplifiedXml</export-type>
		<export-time>2018-02-09T13:54:43.074+01:00</export-time>
		<version>1.0</version>
	</Metadata>
	<Organizations>
		<Organization>
			<PersistentIdentity>22565437447</PersistentIdentity>
			<OrganizationName>1MAN SERVICES<If no such organisation exist, user will not be connected to any organisation. Thus import organisations first. -->
			<CustomerNumber>000069</CustomerNumber>
			<PhoneNumber>18001234567</PhoneNumber>
			<OrganizationName>FOR SERVICE</OrganizationName>
			<OrganizationNumber>SM09049<<PartPriceGroupName>US01</OrganizationNumber>PartPriceGroupName>
			<CustomerNumber>000069<<WarehouseName>US01</CustomerNumber>WarehouseName>
			<Status>New<<MarketCode>US</Status>	MarketCode>
		</User>
	<Email</>
			<PhoneNumber/>
			<FaxNumber/>
			<Note/>
			<Category>Company 2</Category>
			<Addresses>
				<Address>
					<PersistentIdentity>22565423796_1</PersistentIdentity>
					<Name>Active Systems 1</Name>
					<StreetAddress>9995 West Central Entrance</StreetAddress>
					<StreetAddress2/>
					<StreetAddress3/>
					<City>Duluth</City>
					<ZipCode>55802</ZipCode>
					<State>MN</State>
					<Country>US</Country>
					<Type>
						<Primary>false</Primary>
						<Billing>true</Billing>
						<Shipping>false</Shipping>
					</Type>
				</Address>
				<Address>
					<PersistentIdentity>22565423796_2</PersistentIdentity>
					<Name>Active Systems 2</Name>
					<StreetAddress>9995 West Central Entrance</StreetAddress>
					<StreetAddress2/>
					<StreetAddress3/>
					<City>Duluth</City>
					<ZipCode>55802</ZipCode>
					<State>MN</State>
					<Country>US</Country>
					<Type>
						<Primary>false</Primary>
						<Billing>false</Billing>
						<Shipping>true</Shipping>
					</Type>
				</Address>
				<Address>
					<PersistentIdentity>22565423796_3</PersistentIdentity>
					<Name>Active Systems 3</Name>
					<StreetAddress>9995 West Central Entrance</StreetAddress>
					<StreetAddress2/>
					<StreetAddress3/>
					<City>Duluth</City>
					<ZipCode>55802</ZipCode>
					<State>MN</State>
					<Country>US</Country>
					<Type>
						<Primary>true</Primary>
						<Billing>true</Billing>
						<Shipping>true</Shipping>
					</Type>
				</Address>
			</Addresses>
		</Organization>
	</Organizations>
</Export>

Users

Input format

Here is an example of users xml.

<?xml version="1.0" encoding="UTF-8"?>
<Export>
	<Metadata>
		<export-type>SignifikantSimplifiedXml</export-type>
		<export-time>2018-02-09T13:54:43.074+01:00</export-time>
		<version>1.0</version>
	</Metadata>
	<Users>
		<User>
			<UserName>john@mycompan.com</UserName>
			<Title>Mr</Title>
			<FirstName>John</FirstName>
			<LastName>Doe</LastName>
			<Email>john@mycompany.com</Email>
			<!-- Note that this is matched to organisations so user will be connected to organisation with the customer number specified. 
			If no such organisation exist, user will not be connected to any organisation. Thus import organisations first. -->
			<CustomerNumber>000069</CustomerNumber>
			<PhoneNumber>18001234567</PhoneNumber>
			<OrganizationName>FOR SERVICE</OrganizationName>
			<PartPriceGroupName>US01</PartPriceGroupName>
			<WarehouseName>US01</WarehouseName>
			<MarketCode>US</MarketCode>
		</User>
	</Users>
</Export>

Assets

Currently there is no transformation for the asset data. To import assets it is likely that a customize module is required to maintain all business data in exports. One simple example of an asset looks like.

<Asset>
	<Serialnumber>1234567</Serialnumber>
	<ArticleNumber>PROD-123</ArticleNumber>
	<Image>Default.png</Image>
</Asset>Users>
</Export>

Assets

Currently there is no transformation for the asset data. To import assets it is likely that a customize module is required to maintain all business data in exports. One simple example of an asset looks like.

<Asset>
	<Serialnumber>1234567</Serialnumber>
	<ArticleNumber>PROD-123</ArticleNumber>
	<Image>Default.png</Image>
</Asset>

Settings for testing

Importer service has a few extra settings intended for testing purposes, which may be used for error search.

<?xml version="1.0" encoding="utf-8"?>
<CustomFolderConfiguration xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
	<Enabled>true</Enabled>
	<!-- In case SaveItem is true, importer service will save imports directly to the database. In this case importer service will 
	need to know where to find the server.config file since it may be either in AppData or in Program data depending on if importer 
	service is installed on Manager Server or on Web Server. -->
	<ServerConfigPath>C:\ProgramData\Signifikant\Assert\server.config</ServerConfigPath>
	<!-- Log files placed here. -->
	<LogFolder>C:\Signifikant\Log\ImportLog</LogFolder>
	<!-- File watcher will be recreated every x hrs. Default is 0 which means no recreation. Setting available from version 5.1.7 and later. -->
	<SuperviseHours>48</SuperviseHours>
	
	<Settings>
		<CustomFolderSettings ImporteXXXrId="X">
			<!-- Additional options for testing -->
			<Options>
				<!-- Delay each import a bit to simulate longer processing time -->
				<Option key="Delay" value="200" />
				<!-- Auto create a set of files to import, batch size defines how many -->
				<Option key="BatchSize" value="10" />
				<!-- Source folder for test import files -->
				<Option key="SourceFolder" value="C:\Temp\ImportTestInput" />
				<!-- Test logs are separated from normal logs and written at this location -->
				<Option key="LogFolder" value="C:\Temp\ImportTestLog" />
			</Options>
		</CustomFolderSettings>
	</Settings>
</CustomFolderConfiguration>

Related articles

...