•Data Management Configuration
Summary
Script Name |
Add Affiliations to Customers |
|
Minimum Supported Version |
7.24.0 |
|
Source Type |
Single Source |
|
Script Definitions |
Affiliation Load |
|
Use Case
The Add Affiliations to Customers script adds affiliation information in the existing customers.
Source File Format
This script is run using a single .CSV or BI (saved as a text/csv 'Extract Tempate') source file.
The following image illustrates the structure required:
The following table outlines the field mapping:
Column |
Required? |
Source Column Header |
Field Name |
UI Field Location |
1 |
Yes |
customer |
'Customer Number' / 'Customer ID' / 'Legacy Account Number [1-3]' (Used as a Source Key Column) |
Customer Services - Customer|Basic page |
2 |
Yes |
affiliation_name |
Affiliation |
Customer Services - Customer|Advanced page |
3 |
Yes |
affiliation_start_date |
Start Date |
Customer Services - Customer|Advanced page |
4 |
No |
affiliation_description |
Description |
Customer Services - Customer|Advanced page |
5 |
No |
affiliation_end_date |
End Date |
Customer Services - Customer|Advanced page |
6 |
No |
affiliation_comment1 |
Comment 1 |
Customer Services - Customer|Advanced page |
7 |
No |
affiliation_comment2 |
Comment 2 |
Customer Services - Customer|Advanced page |
8 |
Yes |
affiliation_key |
Used as a unique identifier by the script. |
Used as a unique identifier by the script. |
How the Script Works
The following table outlines the actions and expected results of the script:
Condition |
Action |
Expected Results |
The 'Customer Identifier' field in one the Data Management|Schedule page is used to map to the 'customer' in the source file. For example, if Legacy Account Number 1 is selected from the 'Customer Identifier' field then the values entered in the 'customer' column of the source file will be used to load the correct customer using 'Legacy Account Number1' field. |
The script tries to load the Customer using values provided in source file under 'customer' column. |
If the customer is found then the the affiliations will be added. If the customer is not found an error is thrown. |
Affiliations are added under the loaded customer if the required 'Affiliation' and 'Start Date' fields are provided. |
Add affiliations to the customers loaded successfully. |
If required fields are missing an error will be thrown. |
More than one affiliations can be added by providing same values under the 'customer' column in the source file. |
For example, to add three affiliation records under the same customer, supply the 'customer' column with the same customer values for three rows. |
In this example, three affiliations will be added under the customer. |
Data Management Configuration
The following outlines the data management job configuration:
•Data Management Job Name: Affiliation Load
•Script Definition: Affiliation Load
Job Criteria Section |
|
Field |
Field Values |
Customer Identifier |
Any value from the customer identifiers list can be used, based on the values in the source file to identify a customer uniquely. The default value is set to Customer Number. |
The following image is an example of the Data Management|Schedule page when creating a job using all of the available source files:
