data warehouse - How to indicate that one role-playing date dimension is the "primary" (much more popular) date? -

many fact tables in our relational data warehouse have "primary" date other dates. how should indicate prioritization in data model applications built on top of data model guide users toward "primary" date default?

for example, in sales fact table, there's "sale date" column primary date, "recording date" that's seldom used in reporting.

another example: warehousereceiving fact table has "delivery date" column primary, "transaction entry date" used.

is there convention how model 1 role more important others when there role-playing dimensions?

or trying define primary role bad idea because confuse users in case there's not natural "primary" role?

our platform sql server 2014 if matters, question intended platform-neutral.

there no "primary" concept in role playing dimensions.

each dimension , role there business reason. in case sale_date , delivery_date important, perhaps want question role of recording_date , transaction_entry_date, may not play part in business process.

let's assume have sale_date , delivery_date. more important? neither. both. depends on perspective of person writing query.

when dealing fact tables containing multiple dates, 1 technique use order date columns usual sequence in business process. example, date_ordered comes before date_shipped, comes before date_invoiced , date_paid. keeping date columns together, , sequenced, may familiarise casual bi user data.