Glenn Van De Locht Ferranti Computer Systems (MECOMS) Product architect

Request to rework the Case Subject entity to make it more user-friendly for service agents. Missing features for the current Case Subject entity: - Textual search --> being able to type in the subject lookup field (so a service agent doesn't need to drill-down the whole tree every time again) - Multi-lingual support (when you have service agents in multiple countries) - Make subject entity extendable so partners/customers can extend this logic - Make it possible to write a custom pcf control on the case subject field so partners/customers can customize the tree control to their specific needs. The same feedback can be found on several community forums.

Currently no bank account nor a (direct debit) mandate can be registrated for a customer (account or contact) in Dynamics 365. When you do sales with your customers (B2C or B2B), most likely a bank account is required. If the customer wants to pay by direct debit, a mandate needs to be registrated. Currently this is only out-of-the-box supported in Finance and Operations (back office) but a service agent (front office) in Dyamics 365 should be able to create a new bank account/mandate, change the customer payment details and bank account when a customer calls to the support organization. Idea would be to implement something similar in Dynamics 365 Customer Service or Sales like it's implemented in Finance and Operations (in this way, integration between Dynamics 365 and Finance and Operations would be easier making use of Dual-Write/Virtual Entities).