Dynamics 365 Tasks

Carolina Salazar 0 Reputation points
2026-11-19T15:44:56.55+00:00

I have a custom task in Dynamics, and it contains levels and order. Can someone please guide me on how the levels work for Microsoft Dynamics 365 Custom Tasks?

Microsoft 365 and Office | Development | Other
0 comments No comments

Answer accepted by question author
Hendrix 2,855 Reputation points Independent Advisor
2026-11-19T16:11:05.6066667+00:00

Hi Carolina,

Regarding your concern, the Level and Order fields are not standard fields with the same meaning in Microsoft Dynamics 365 tasks. In a custom Dynamics solution, Level represents the task’s hierarchy, while Order determines the sequence of tasks within the same level. However, the exact behavior depends on how your custom table and automation were configured.

That said, for you to receive the best assistance for this concern, I recommend posting your scenario in the Dynamics Community Forum Thread. This forum is dedicated to Dynamics 365 and is actively monitored by experienced users, Microsoft partners, and engineers who can provide detailed guidance and share best practices.    

I apologize for redirecting you to a different community, as the members of this category focus on Office 365 concerns and have limited knowledge about Dynamics 365. To help you get quicker and better assistance, I'm guiding you to the best resource. When posting your question in this community, you'll get the most qualified group of respondents, and other partners who read the forums regularly can share their knowledge or learn from your situation.  

I hope everything gets sorted out soon.

Was this answer helpful?

1 person found this answer helpful.

1 additional answer

Sort by: Newest
  1. AI answer

    2026-11-19T15:46:57.9833333+00:00

    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^

    Check the column metadata

    In the Power Apps maker portal:

    1. Select the environment used by Dynamics 365 Customer Service.
    2. Open Solutions, then open the solution containing the task configuration.
    3. Select Tables → the relevant task/configuration table → Columns.
    4. 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
    5. Do the same for Order.
    6. 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

    1. Task table/entity reference (Microsoft Dynamics 365 Customer Service)
    2. Configure and manage agent scripts
    3. Configure bullseye routing using conversation orchestration playbooks | Microsoft Learn
    4. Configure Case Management Agent
    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.