Process for Mapping Sales Files
sales_schema_mapping = where the standard Sales file mappings live. Generally, DO NOT MODIFY this as it will affect ALL sales files loaded!
sales_schema_mapping_custom_headers = where custom mapping for individual dealership Sales files live. Here, you can custom map columns in sales files for each dealer (for each unique folder in Dropbox\IDD\0-Sales).
- folder_name = the rooftop folder from Dropbox\IDD\0-Sales
- alias_fingerprint = the column name from the Sales file (all lowercase, no spaces or punctuation EXCEPT DO include #)
- target_filed = the target field name as taken from sales_schema_mapping table target_field
Remember to commit changes!
Mapping Multi Files
What are Multi Files?
A (multi) file is when a dealer or vendor includes data for multiple stores in 1 file. The file MUST contain a Dealership Name column with the following rules:
- The Dealership Name column must be populated on all data rows. It cannot be left blank or the file will get stuck due to an error.
- The Dealership Name column must have unique values for each dealership.
- The values must not be generic values such as 1, 2, 3. They must be unique values such as the store name, or an ID number consisting of 4 or more digits.
Mapping a (multi) file needs to be done for:
- Multi files loaded through Dropbox Insyncing Data Drop folders.
- This may include files received in the SFTP that get transferred to Dropbox Insyncing Data Drop by a DAG (example: Tekion Sales)
- Leads files pulled by Wall-E/the scraper. See Data Integration: Scraper Method for information on how to obtain the property aliases from each vendor system.
Process for Mapping Multi Files
- Insert rows into the claripedia -> tables -> property_aliases table
- property_alias = the name of the property in the Multi file *property column - ALL lowercase, no punctuations or spaces EXCEPT DO include #
- property_id = Clarivoy property ID
- Remember to commit changes!