Profile a field's shape before you build on it

The task

Scenario. An analyst is about to aggregate on a field they've never used, an `amount` or `status` column, and needs a quick profile first: what type it really is, how many nulls, how many distinct values, and its range. Building on a field that's secretly 40% null, stored as text, or dominated by one value is how a report goes wrong before it starts.

The ask

• The field's data type, null rate, distinct count, and range
• Whether its real shape matches what you were about to assume
• Anything about it that makes it risky to build on

Hero prompt

Step by step

1. 1

   Find the field.

   Step 1

   Copy

   Find the <amount> field on <table> and confirm it's the one I mean.

2. 2

   Quick-profile its shape.

   Step 2

   Copy

   Profile it: data type, null count and rate, number of distinct values, and its min/max range.

3. 3

   Flag anything that makes it risky to build on.

   Step 3

   Copy

   Tell me if anything here would break a report: a high null rate, a text type where I expected a number, or one value dominating the field.

What you'll give it

Required context

• The table and field
• Read access to the connected source through Atlan, with query permission

Optional context

• What you're about to build (a sum, an average, a join), so the profile can call out what specifically would break it
• The type or range you expect, so it can flag the gap

What Atlan creates

Outputs

• The field's real data type, null count and rate, distinct-value count, and min/max range
• A plain read on whether it's safe to build on, with the specific risk called out

Summary. You know the shape of the field, not just its name, before you aggregate or join on it, so you don't discover a 40%-null column after the numbers look wrong.

Follow-up prompts

Keep going once the first answer lands.