SETUP GUIDEHow to set it up8 sections. Choose a role to highlight what matters to you.
Everyone
1What it is and why
What it is
A setup page where you define the priority codes that you assign to lead records.
What you do here
Use this page to rank leads so that sales people work the most urgent ones first.
Example
BEAT defines the priorities HIGH, MEDIUM and LOW. A lead for a 25,000.00 USD equipment order, LEAD-000418, gets priority HIGH, and the sales manager's morning list shows the 6 HIGH leads before the 41 MEDIUM ones.
The page in Dynamics 365. page title tab to open what to set or check
About the examples: Examples and screenshots in this guide use BEAT, a demo company in a Dynamics 365 test environment. Use your own company's codes and values instead of copying them.
Step by step, with screenshots
Set up Priority1 screen
Use this page to give lead records a priority.
Screen 1
Create a lead priority
Go to Sales and marketing > Setup > Leads > Priority
Select New
Enter the priority code and description
Select Hot alert if leads with this priority need attention first
Select Save
1Priority
BEAT-PRI
Description
Priority
Hot alert
No
Show the full screen page title tab to open what to set or check
How to use it
Go to Sales and marketing > Setup > Leads > Priority.
Select New and enter the Priority code, such as HIGH, and a Description that says how fast the lead must be followed up.
Set Hot alert to Yes or No for the priority.
On All leads, open a lead and select the new priority to check that it is offered.
Source: Checked in Dynamics 365
Fields on the page
Field
What it means
Example
Table column
Priority
The code of the priority, for example HIGH. It is the value you select in the priority field of a lead.Microsoft data model
HIGH
Priority
Description
A short description of the priority.Checked in Dynamics 365
Call within one day
Description
Hot alert
A Yes/No option stored with the priority (column MCRHotAlert). The live system shows No for the BEAT priority.Checked in Dynamics 365
No
MCRHotAlert
Common errors and fixes
Message
What to do
Two codes mean the same urgency, so leads are split between them and the HIGH list looks shorter than it is.
Keep one code per level. Reassign the leads on All leads to the code you keep, then delete the duplicate code. Microsoft data model
Test checklist
Create the priorities HIGH and LOW.
Give two leads on All leads the priority HIGH and one lead the priority LOW.
Three to five priority codes with a description that states the follow-up time (for example HIGH: call within one day).The priority code is stored on each lead, so a description with a clear follow-up rule makes the code mean the same to every sales person.
Reversible: Priorities can be changed or removed; leads keep the code they were saved with.
If you change it later
The lead stores the priority code (Priority), so adding or renaming a priority changes what sales people can choose and how lead lists sort. Existing leads keep their code. Microsoft data model
Technical architect
6Technical
Menu item
smmLeadPriorityChecked in Dynamics 365
Form
smmLeadPriorityTableChecked in Dynamics 365
Table
smmLeadPriorityTableShown as “Lead priority” in Record infoChecked in Dynamics 365
PrivilegesMaintain lead priorities smmLeadPriorityMaintainView lead priorities smmLeadPriorityViewDutiesEnable the Sales and marketing process smmCRMProcessEnableInquire into Sales and marketing reference data smmCRMReferenceDataInquire2 security rolesInformation technology manager SysServerITManagerSales manager TradeSalesManagerChecked in Dynamics 365
Roles to set it up and use it
To set it up or change itSales manager TradeSalesManagerInformation technology manager SysServerITManagerGive people one of these roles. On this system, 2 roles can open this page.Checked in Dynamics 365
Actions on the page
Options: Personalize, Page options, ShareChecked in Dynamics 365
smmLeadPriorityEntity (Lead priorities): loaded for each company, in Microsoft's default template 330 - Sales and marketing.Load order: Microsoft's default template 330 - Sales and marketing loads Lead priorities at execution unit 1, level 30, sequence 10. Lower levels load first, and entities at the same level load in sequence order.Load first: the default templates at lower levels (System setup to General ledger)Microsoft Learn
Checked in a working Dynamics 365 system, version 10.0.49: the menu item, form, table and security, the page, the demo records and the values in the screenshots.
To cite this step: SM-SETUP-150, Set up Priority. Beyond ERP Atlas Hub, 2026-11-11. https://www.beyonderp.cloud/atlas/step/SM-SETUP-150