Embedded data changes

Hi ​@donnjak,

Have you tried exploring Manual Fields AND Bucketing Fields?

Assuming your data has already been collected, you can create a new field using bucketing. Just ensure that both Level 1 and Tier 1 are derived from the same question or variable. If the source variable is numeric, you can define a range and capture both categories within a single new field. Once the bucketed field is created, it will be applied to the existing dataset as well as to all new responses moving forward.

Hello, donnjak

Dealing with a shift in sales hierarchy nomenclature can be a headache, but you definitely don't have to manually edit every single response to get your data aligned. The most efficient route is to start by adding your new embedded data fields directly into the Survey Flow at the top—just make sure the names match your directory exactly, including the casing and spaces. Once those are in, you can update your contact list in the XM Directory with the new values.

To get that updated info into your existing data, use the "Update All Responses with Current Metadata" tool found in the Participants tab. This pushes the new values into your dataset in bulk so you don't have to touch them one-by-one. If you need to update the directory itself, exporting the participant list to a CSV, making your changes, and re-importing it with matching Unique Identifiers is the standard way to avoid creating duplicates.

Just remember that if you've already collected a ton of data and need to add these fields retroactively, you'll want to ensure those fields are in the Survey Flow before you start the import process. If things get tricky with the re-importing or if the metadata isn't mapping as expected, it might be a good idea to have a support specialist take a look at your specific project setup. You can reach out to the team through the Customer Success Hub to ensure your hierarchy stays intact: https://support-portal.qualtrics.com/ 📈

Thank you both for the replies. I really dislike importing/re-importing as prior experience with not as large of a project led to a mess (totally user error). I chickened out and contact support specialist who was excellent and did it for me in no time.