|
|
| (2 intermediate revisions by one other user not shown) |
| Line 1: |
Line 1: |
| − | = Initiating Internal Churn in Bulk =
| + | {{DISPLAYTITLE:Initiating Internal Churn in Bulk}} |
| | + | =This Content Has Moved House= |
| | | | |
| − | This feature provides a method to commence the internal churn process for a given list of source package subscriptions & destination account id's / package plan id's. | + | 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 we 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/Internal+Churns 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 ==
| + | [[file:new_home_sm.jpg|900px]] |
| − | 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.
| |
| − | | |
| − | [[File:bulk-internal-churn-sample.csv|Sample CSV File]] | |
| − | | |
| − | 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 to the system, 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.
| |
| − | | |
| − | == Initiate Bulk Internal Churn ==
| |
| − | | |
| − | Access to this bulk upload facility may be restricted to those subscribed to it.
| |
| − | | |
| − | To access the Bulk Internal Churn facility:
| |
| − | | |
| − | # Log into Cumulus.
| |
| − | # '''Nav: Admin > Bulk Import > Bulk Internal Churn'''.
| |
| − | # 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'''
| |
| − | | |
| − | [[File:Bulk-internal-churn.png|Bulk InternalChurn]]
| |
| − | | |
| − | 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.
| |
| − | | |
| − | === Bulk Internal Churn - Data Definition ===
| |
| − | | |
| − | {| class="wikitable"
| |
| − | |+Bulk Internal Churn Data Definition table
| |
| − | |Data field ||Description
| |
| − | |-
| |
| − | |package_subscription_id || This is the current PACKAGE SUBSCRIPTION ID of the originating services you are intending to internally churn.
| |
| − | |-
| |
| − | |destination_account_id || The new ACCOUNT ID of the account you are intending to internally churn to.
| |
| − | |-
| |
| − | |transfer_date || This is the DATE (DD/MM/YYYY) you wish for the new package subscriptions to be active
| |
| − | |-
| |
| − | |package_plan_id || This is the destination PACKAGE PLAN ID. The destination plan:
| |
| − | * must be of the same structure as the originating package
| |
| − | |}
| |
| − | | |
| − | Your finished data file should look like the following example.
| |
| − | | |
| − | {| class="wikitable"
| |
| − | |+Bulk Internal Churn Data File Example
| |
| − | | package_subscription_id || destination_account_id || transfer_date || package_plan_id
| |
| − | |-
| |
| − | | 1234567 || 1999998 || 1/01/2016 || 199888
| |
| − | |-
| |
| − | | 2134567 || 6999998 || 1/01/2016 || 199887
| |
| − | |-
| |
| − | |}
| |
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 we appreciate your patience during the transition to out new home.
