Launch Deal · 50% off 1st month ·

2.1 — Configure Table and Column Properties

PL-300 Domain 2 · Skill 2.1

What You Need to Know

Properties are set in Model view (or the Data view and Column tools ribbon) in the Properties pane. They don't change the data. They change how fields behave and look for everyone who builds reports on the model.

Column properties

Property What it does Typical use
Name and Description Display name; description shows as a tooltip in the field list Business-friendly names
Synonyms Other words Q&A and Copilot recognize "Revenue" for Sales Amount
Display folder Groups fields into folders in the field list Many measures in one table
Is hidden Hides the field from report view Keys, sort columns, columns used only by measures
Data type and Format Storage type; display format (currency, %, decimals, thousands separator, date format) Show 0.25 as 25%
Sort by column Sorts a column by the values of another column Month Name by Month Number so months don't sort alphabetically
Data category Tells visuals what the values mean: Address, City, Country, Postal code, Latitude, Longitude, Web URL, Image URL, Barcode Maps geocode correctly; URLs become links or images in tables
Summarize by (default summarization) Sum, Average, Count, Min, Max… or Don't summarize Set Year, Product ID and similar numeric columns to Don't summarize
Is nullable Fails refresh if a blank appears Key columns

Sort by column rule: the sort column must have exactly one value for each value of the column being sorted. Month Name sorted by a Date column fails, because each month name has many dates.

Table properties

Property Use
Name, Description, Synonyms As for columns
Row label The column that best describes a row, used by Q&A and Copilot
Key column The unique column of the table
Is hidden Hides a whole helper table
Storage mode Import, DirectQuery or Dual (lesson 1.2)
Is featured table Makes the table available in Excel's Organization data types

Model-wide clean-up worth doing

  • Hide foreign key columns in fact tables. Users should slice by dimension attributes, not by keys.
  • Create explicit measures (Total Sales = SUM(Sales[Amount])) and hide the numeric columns they wrap. Setting the model property Discourage implicit measures stops report authors from dragging raw columns into values.
  • Use display folders and descriptions so the field list explains itself. Copilot and Q&A also use names, descriptions and synonyms.

Key Concept: Properties shape the experience of everyone who uses the model: correct sort order, formats, geography, default aggregation and a clean field list. Most "the visual shows the wrong thing" questions are fixed with a property, not with DAX.

Exam Traps

  • Writing a DAX column to sort months when Sort by column is the fix
  • Sorting by a column that has several values per sorted value (the sort fails)
  • Leaving Year or Customer ID summarized as Sum
  • Setting a city column's data category to Address, or leaving it uncategorized, when the map plots cities in the wrong country (also add State or Country, or build a hierarchy)
  • Hiding a column and expecting it to be secured (hidden fields can still be queried; use object-level security for that)

Check your understanding

Practice Scenario

🔒 This practice scenario is part of Skillmarked Pro

The lessons stay free. Pro unlocks the other 22 PL-300 practice scenarios and the 50-question timed mock exam, plus everything for every other exam.

See plans

Launch Deal: first month €9.95, then €19.90/month. Enter code LAUNCH50 at checkout. Ends 1 December.

Cancel anytime. Or €199 a year, which saves 17%.

Not sure yet? Try 10 free mock exam questions.

Already Pro? Log in.