Stefan Faust Manager

One of e.g. Salesforce's (or other software products) strength is the possibility to specify within an entity different "record types", to cover within one system different business processes. Having different business processes allows to implement a software within multi-divisional or -country organizations. From my point of view this is one major reason why Dynamics cannot be really considered in many large enterprises projects! A record type could specify e.g. 1. Form Layout 2. Security role(s) 3. Option set values 4. Settings to influence the business process 5. Workflows and rules 6. Business process flows A record type could be * in account e.g. "Wholesaler", "Direct Customer", "Indirect Customer", … having different processes how to maintain and what to maintain, who can maintain. Furthermore quite often such types specify, where to use such an account type. E.g. you would not create a Quotation to an indirect customer, but to direct customer only. * Quote Types with different Layouts, fields, conditions, approval processes, considered stakeholeders, ... * Opportunity types for different purposes like multi- or single-country or single-or multi-year opportunities, ...

Different user roles require within one system different different System views and data to be seen. Today a System view can not be set up differently per user role (e.g. Sales rep, Sales Manager, Service rep, …) or division or Country within an organization. Similar like forms it should be possible to assign views to security role(s) and to provide appropriate experience to user. (valid for all Dynamcs Engagement Solutions)