Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Import Macro Repair

This guide describes Please reference the /wiki/spaces/rtd/pages/2753046, which contains the suggested steps for migrating customers from Classic EIS to Inventory. The article assumes that the district instance has already been configured as described in Production Release#SettingupaDistrictInstance

Step-by-step guide

...

  1. Ask Jason Klinger  about parameters

...

Review the resulting import.log file for errors - ask Jason Klinger for the name of the file.

...

titleThis was copied from the USAS file, if it doesn't apply edit or remove it

The end of the import log will have a binary status that will indicate whether the importer ran to completion. It will appear similar to the following example.

districtname_usasimport_1 exited with code 0

A code of 0 indicates the importer ran to completion whereas a code of 1 signifies the importer terminated with an unknown exception.

...

.

...

 

...

Review the information on the Post Import Procedures page.

Once a successful import has been certified we recommend immediately creating a database backup using the /ssdt/script/backup-usps.sh script.

...

Filter by label (Content by label)
showLabelsfalse
max5
spacesFSKB
showSpacefalse
sortmodified
reversetrue
typepage
cqllabel = "kb-how-to-article" and type = "page" and space = "FSKB"
labelskb-how-to-article

...

Page Properties
hiddentrue


Related issues