Updating Hierarchy Data
Updated
This functionality assists you in arranging survey data in line with your organization’s hierarchy, facilitating easier access and analysis of pertinent information for teams at various levels. The organized method guarantees that feedback data can be efficiently leveraged across numerous survey initiatives. Important features comprise:
Sprinklr’s organizational hierarchy features make it easy for teams to manage and analyze feedback across complex structures. Granular insights allow you to drill down into specific segments, such as individual stores, departments, or regions, to identify targeted areas for improvement. Customizable dashboards automatically deliver role-specific reports to managers and senior leaders, eliminating the need for manual setup. Admins can keep hierarchy data up to date with dynamic updates by uploading only the rows that need changes through Excel, simplifying ongoing data management. With a one-time setup, the hierarchy is configured through a guided Excel or CSV upload and can be reused across multiple survey projects, ensuring consistency and saving time.
Refer to the introductory article to understand more about the use cases, value additions, and prerequisites.
Prerequisites
At present, the Hierarchical reporting feature is included by default in CFM. However, to configure a data connector, the following permissions are necessary.
Permissions for Setup Data Connectors include Viewing, View Audit Logs, Create, Edit, Delete and Dmp Share.
Setting Up
For manual data updates, no extra configuration is necessary for this feature; the prerequisite is that you must have a hierarchy established previously.
To establish a recurring data connector, you need to have a hierarchy in place and the necessary permissions for the data connector.
How to use it?
Manual Data Update
Accessing the Update Option: Click on the Vertical Ellipsis any of the Hierarchy and click View Data or View Set up.
View Data Screen:
The "View Data" screen shows the present status of the hierarchy data saved in Sprinklr.
You can click on + Update Data.
View Setup Screen:
The "View Setup" screen displays the configurations established during setup that link the ingested organizational fields to the Sprinklr hierarchy fields.
Updating Hierarchy Data:
You can start the Hierarchy Data Update Flow from either the "View Data" or "View Setup" screen. To refresh the hierarchy data, you need to create an updated file that follows the same structure as the one used in the initial hierarchy setup.
Note:The update file does not substitute the data that was uploaded earlier. It is designed to either modify current records or generate new ones using the Unique ID. Users should include only the records that need updating or any new records they want to incorporate in the update file.Downloading Templates:
You can download a template, complete it with the necessary information, and then upload it for updates.
Uploading the update file:
You have the option to use the “browse” feature to choose and upload a file from your device.
The initial sheet of the file is automatically chosen, but you have the ability to modify the selected worksheet according to their needs.
Importance of the Unique ID Field:
Changes to the hierarchy rely on the "Unique ID" field, which serves as the primary reference point.
When new records are uploaded through file, the following conditions are fulfilled.:
If a record featuring the same Unique ID is already present, the relevant fields will be updated according to the information in the file.
If there is no corresponding Unique ID, a new record will be generated.
For this document we have considered the Unique ID to be the “Store ID” field, but can be anything
If Unique ID is missing from the sheet uploaded for updating the hierarchy data the user sees the following “un-skippable” error.
Adding a New Field to the Hierarchy
When a file is uploaded to refresh data, the column names within the file are verified against the mappings established during the hierarchy configuration. Consequently, the column names need to correspond with those specified in the initial setup.
Only the "Unique ID" column is mandatory; all other columns are optional.
If the updated data file includes columns that are not currently associated with any hierarchy field within that hierarchy, you will be alerted with a warning that lists the names of these unmapped columns.
You can then choose one of the following options:
"Save without Mapping": Disregard the additional columns.
"Save and Map Column": Associate the new columns with the Sprinklr Hierarchy Fields.
Save and Map Column Flow for adding new fields in Hierarchy:
The "Save and Map Column" option allows you to:
You need to enter the Setup Screen and map these new columns to Sprinklr fields.
Assign the new columns to the Hierarchy field at any existing level, or establish a new highest level within the hierarchy.
You can see the names of these columns in the Column selection dropdown while mapping. In this context, we note that the “Region Governor” column can be linked to a hierarchy field at Level 3, related to “Region” fields. The mapping process follows the same procedure as the Setup.
A new highest level may be incorporated into this flow; however, it is not possible to insert a level between two already established levels.
You can assign the columns and click save for the changes to be applied to the hierarchy. These can be confirmed through the View data screen.
Note: No changes can be made to fields already mapped in the hierarchy.
Only new fields can be created and mapped to the new columns.
New levels can only be added at the highest level.
A new level cannot be introduced between two existing levels.
Combining Use Cases
You can accomplish any combination of adding new records, updating current ones, or introducing new fields by following the steps outlined above and preparing the update file appropriately.
Recurring automated updates through Data connector
Once you have established the hierarchy for the data connector you want to configure, navigate to the "Global Settings" option within the Customer Feedback Management app and then click Data Connectors under Program Settings.
By selecting the “Data Connectors” option, you will be able to view a list of all previously set up data connectors for Customer Feedback Management related entities such as Hierarchy, Transaction, and Response.
Click “+ Install Connector” option to create a new connector.
Creating a connector: Select the entity type for which you want to create the connector. Hierarchy entity is listed as “CFM Hierarchy” then select and click on next.
Go to Entity Specific Settings screen and fill details:
Hierarchy: You have the option to choose the specific hierarchy for which we intend to establish the update connector. You can select one of the previously configured hierarchies and also can also search for the hierarchy by name:
Integration Type: Choose the type of integration. You may select "Upsert" as it is the only supported type, allowing the connector to either create new records or update existing ones.
Source Selection Screen: At present, Data Connector supports SFTP, Azure Blob, S3, and GCS. For file-based upserts, users can utilize the built-in "Update data" flow available in the Hierarchy screens.
Source Specific Settings: You need to provide the specific connector information according to the type of source in use. Refer to these articles for more connections:
Additional Settings screen: You can specify the intervals for the connector's operation, and you can also configure notifications to receive updates for each run.
Refer to this article for further details.
After this, the connector is configured, and you can now activate and operate it.
Running and Activating the connector
Inorder to manage Data Connectors you can click on the Vertical Ellipsis (⋮) to access the data connector management options:
Edit: You can modify the details of the data connector and adjust the run intervals. After setup, the user cannot change the source type.
Delete: You can delete a connector.
Run: You are prompted to upload a file based on the connector's specific configuration. The system processes this file to create or update the necessary entities. For a one time on demand run.
Activate: You can enable the connector using this option, and once activated, it will automatically operate according to the time intervals specified in the additional settings screen.
View Activity: You can access the logs detailing the modifications made to the connectors, as well as the run history that includes success and failure files for each execution.
Case of records failing in data connector:
Unique ID column was missing the received file : This would cause the entire file to fail.
Duplicates in the Unique ID column found: The initial instance would be utilized, while all subsequent ones would fail.
If a new column needs to be mapped for ingestion, this should be done through the “Update Data” option found in the Hierarchy screen.
Note: You can test it in the following way:
Like the examples presented in the article, you can manually examine a few records after saving the updated data file to check if the changes are reflected in the view data screen.
Create and submit the updated data file incorporating the necessary modifications (such as new records, field updates, or the addition of new fields).
Navigate to the View Data screen.
Identify a few sample records from the update file and compare their values in the View Data screen.
Make sure that the revised fields correspond with the information in the file.
Ensure that the new records have been added accurately.
Verify that the newly added fields are displaying correctly and include the updated values where necessary.
At present, the linking is solely dynamic, meaning that the analytics results will change dynamically in response to any modifications or updates made to the hierarchical data.
Best Practices
Maintain Column Consistency:
Ensure that the names of the columns in the revised data file exactly match those set during the original configuration of the hierarchy mappings.
The “Unique ID” column is the only required field; all other columns are optional.
Unique ID is Key:
Always ensure that the “Unique ID” column is included in the update file, as it serves as a reference for aligning records.
Eliminate duplicate Unique IDs in the file to avoid any conflicts.
Include Only Necessary Records:
Only include the records that require updates or new entries. It is unnecessary to re-add the complete hierarchy data.
Format for New Fields:
When incorporating new fields (such as "Country President" or "Region Governor"), make sure to add these fields as additional columns in the updated data file, ensuring they are correctly mapped during the upload process.
Make sure that the new column detection is genuinely a new field rather than a mistake in the column name.
Template Utilisation:
Utilize the supplied template as a foundation to guarantee the proper structure and format of the update file.