|
|
| (5 intermediate revisions by the same user not shown) |
| Line 1: |
Line 1: |
| | {{DISPLAYTITLE:Service Identifier Vanity Names Import}} | | {{DISPLAYTITLE:Service Identifier Vanity Names Import}} |
| − | = Overview = | + | =This Content Has Moved House= |
| − | This feature provides an easy and fast way to update existing service identifiers with vanity names via a bulk upload tool. Creating new service identifiers with vanity names is not supported via the tool and can be done using the [[Services/Service_Identifier_Management|Service Identifier Management]] section of Cumulus. | + | This article has been moved to our new home for documentation and help content, the new Emersion Knowledge Base. |
| | | | |
| − | The system utilises the '''Bulk upload processing notification event''' to send a notification with the results of the import attempt. See below for further information.
| + | We are sorry for the untidiness while we are shifting locations, and appreciate your patience during the transition to out new home. |
| | | | |
| − | If the import is successful, the email notification will advise you when the import process is complete. <br />
| + | [https://resources.emersion.com/display/EKB/Service+Identifier+Vanity+Names Take me to the Emersion Knowledge Base article] |
| − | If the import is not successful, the email notification will send details of the records that failed validation and why.
| |
| − | | |
| − | == Preparing your Data ==
| |
| − | To prepare your data for import, you will need to create a CSV import file or you can download the import file below. You will need to extract the csv file and save it.
| |
| − | | |
| − | There is a hard limit of 5,000 service identifiers that can be updated at any one time using the tool. If you need to update more than 5,000 service identifiers at a time, please create multiple import files.
| |
| − | A single import file can have up to 4999 rows of data plus the header row.
| |
| − | | |
| − | [[Media:si_vanity_id_import.zip]] | |
| − | | |
| − | Enter the data into the import sheet. Leave no rows blank. You must ensure the data meets all validation requirements. These are contained in the data definition table below. When you submit the data file for import, the system will parse the file looking for errors. If the system finds no errors, the system will import the notes into the system. The file needs to be error-free in order to import the data. In the event errors are found, no data will be imported into Emersion. Review the bulk upload processing notification email, correct the file and try again.
| |
| − | | |
| − | == Importing your Data ==
| |
| − | | |
| − | To access the note import tool:
| |
| − | | |
| − | # Log into Cumulus.
| |
| − | # '''Nav: Admin > Bulk Import > Service Identifier Vanity Names'''.
| |
| − | # Click the '''Browse''' button and select the csv file containing the data you want to import.
| |
| − | # If you want the bulk upload processing notification email to be sent to a different email address than the address defined in the event template, tick the '''Override?''' checkbox and enter an alternative email address. This will only apply for this upload. To change the email address for all future imports, you will need to change the recipient defined in the event template.
| |
| − | # Press '''Submit'''
| |
| − | | |
| − | The system will validate the data and if no errors are found, the system will import the data. When the notification email is received, the process has been completed.
| |
| − | | |
| − | <strong>'''The system can parse for invalid data but it cannot check for data accuracy. Therefore it is strongly recommended that you check a few random records to ensure that the import was a success. If you find an problem, you cannot roll back the import.'''</strong>
| |
| − | | |
| − | You have two options should this occur:
| |
| − | | |
| − | # Manually correct the data.
| |
| − | # Request Emersion fix the errors for you. This can be submitted via [[Support_and_help_from_Emersion#Work_Orders | work order ticket]]. Please include a note import file with the records that need to be corrected. Do not include details of any records that do not need correcting.
| |
| − | | |
| − | = Data Definition =
| |
| − | This section contains a list of the required fields and a definition of what the system considers as valid data.
| |
| − | | |
| − | {| class="wikitable"
| |
| − | |+Bulk Update for Service Identifier Vanity Names Data Definition table
| |
| − | |'''Data field''' ||'''Description'''
| |
| − | |-
| |
| − | |SERVICE_IDENTIFIER_ID ||The ID of the service identifier that will be updated. This can be found in Cumulus at the this path, '''Customer > Service Subscription > Service Identifiers. MANDATORY'''
| |
| − | |-
| |
| − | |VANITY_IDENTIFIER ||The vanity name. The system supports up to 100 characters. '''MANDATORY''' using the update action and '''OPTIONAL''' when using the delete action.
| |
| − | |-
| |
| − | |ACTION ||Enter the text exactly how it appears:
| |
| − | * Update
| |
| − | * Delete
| |
| − | | |
| − | The ''Update'' action will insert the new vanity name into the service identifier record, overwriting any existing vanity name. The ''Delete'' action removes the vanity name from the service identifier record. The ''Delete'' action does ''not'' delete the service identifier itself, only the data stored in the vanity name field.
| |
| − | |-
| |
| − | |}
| |
| − | | |
| − | = Access Control =
| |
| − | Users will need the '''Bulk Update - Service Identifier Vanity Names''' power in order to use this import tool. This power can be found under the '''Service Identifiers''' power group.
| |
This article has been moved to our new home for documentation and help content, the new Emersion Knowledge Base.
We are sorry for the untidiness while we are shifting locations, and appreciate your patience during the transition to out new home.
