Required attributes are null

Required attributes are required for a reason! Unfortunately, this doesn’t always mean that users fill them out correctly.

Overview

When required attributes aren’t filled out it significantly impacts the value of the data. Image a contact without any email or phone number associated with it or a account without any people. Luckily when the data exists within the system, these values can be augmented.


Impact

Reliability and usability are the key impacts of missing required attributes. Think about service manager who relies on the start date to due their job.

Without this critical piece of information consistently populated, they will establish habits of looking elsewhere (maybe through pages of contracts) to find what they are looking for.


Steps to resolution

Determine Approach 🎯

For agentic data quality to work, you need to have the information in the system somewhere. This may be in meeting notes, the description, or your database.

Once you’ve identified where the information exists, think through how the information should be pulled and applied to the required field.

Navigate to an Example 🕴

Find an example record that is missing the required field. In this example the required field is going to be start date.

Prompt the Assistant 💬

Prompt the adq assistant on the problem (e.g., “The start date field is required for all closed won opportunities and it is null here”) and the solution (e.g., “Pull the start date from the contract data”). Press analyze once the system has been prompted.

Validate Results ✅

Confirm in a few places that this matches up correctly. Once you feel confident about the changes, submit them!

Enjoy the Success 🎉

At this point, you’re basically a data wizard. Data discrepancies and issues should beware! 🧙‍♀️