The Level field cannot be interpreted from its display name alone; identify its Dataverse logical name and owning solution because the standard Dynamics 365 Customer Service Task table does not document a Level/Order field pair.^1^
In the Power Apps maker portal:
- Select the environment used by Dynamics 365 Customer Service.
- Open Solutions, then open the solution containing the task configuration.
- Select Tables → the relevant task/configuration table → Columns.
- Open Level and record:
- Name/logical name, including its publisher prefix, such as
new_level or msdyn_...
- Data type
- Description
- Choice values, if it is a Choice column
- Do the same for Order.
- Check the table’s Relationships for a self-referencing relationship—one task referencing another record in the same table.
These details distinguish three common designs:
- A custom
new_level/similar column means Level is organization-defined. Its behavior must be found in the associated business rule, cloud flow, plug-in, JavaScript, or application documentation.
- A self-referencing task relationship may mean Level represents hierarchy depth—for example, parent tasks at level 1 and child tasks at level 2. Do not assume this unless the relationship or automation confirms it.
- A Microsoft-managed
msdyn_... column can be matched to the corresponding Microsoft table reference by its exact logical name.
What the Microsoft features indicate
The regular Customer Service Task table is a generic activity for work that must be done. Its Customer Service reference does not define Level or Order as standard task attributes.^1^
If these are Unified Service Desk agent-script tasks, progression is configured through answers that lead to subsequent tasks; the documented task fields include Name, Start Task, Show Tab, Category, Script Text, and Instructions—not Level and Order.^2^
“Level” also has unrelated meanings elsewhere in Customer Service:
- Bullseye routing levels concern routing and assignment, not generic task completion order.^3^
- Case Management Agent automation level selects semi-autonomous or fully autonomous operation; it does not describe a task hierarchy.^4^
Therefore, those interpretations apply only if the records are from the corresponding routing or agent configuration—not merely because the field is named Level.
The exact answer requires the table logical name and the Level column logical name. A screenshot showing the table name and column properties—without customer or environment identifiers—would also identify the configuration safely.
References
- Task table/entity reference (Microsoft Dynamics 365 Customer Service)
- Configure and manage agent scripts
- Configure bullseye routing using conversation orchestration playbooks | Microsoft Learn
- Configure Case Management Agent