6
Standard attributes/fields on case entities should be defined as equal between the D365 FO and D365 CE applications, so that this facilitates a better case management cross-application, in support of synchronisation activities (i.e. dual write).
- Case type >< available on D365 CE with a pre-defined option set (question, request, ...), but not available on D365 FO
- Naming/label conventions across applications (Subject vs. Category)
Use case:
Being able to identify from a certain case, what type of case (not origin) this is about, so that the case type can identified. Additionally for a number of implementation in the Utilities industry, we would like to use this also to specifically identify a "Complaint", which is regulated in various markets (UK, Italy, Netherlands, ...).
- Case type >< available on D365 CE with a pre-defined option set (question, request, ...), but not available on D365 FO
- Naming/label conventions across applications (Subject vs. Category)
Use case:
Being able to identify from a certain case, what type of case (not origin) this is about, so that the case type can identified. Additionally for a number of implementation in the Utilities industry, we would like to use this also to specifically identify a "Complaint", which is regulated in various markets (UK, Italy, Netherlands, ...).
STATUS DETAILS
Needs Votes
Comments
Considered case types:
Question
Request
Incident
Problem
Complaint (New)
Category: Data Management