Inheritance on Entities or Copy Entity
I'd like to be able to create a new entity that either inherits the attributes from another entity, or to create a new entity based on a "template" of an entity. For example, we often find ourselves creating new entities similar to contact and account, and it would be so much easier to be abl...
Need high availability to handle CRM Online outages
CRM Portals is dependent on connectivity to CRM Online, and the portal will be down or suffer degraded user experiences when there CRM Online service outages caused by unplanned service interruptions and scheduled maintenance. For example, during an outage, only server-side cach...
Entity Permissions should not trigger linked entities query limit
Entity Permissions modify the FetchXml when retrieving data from the CRM. This often results in getting a 'Number of link entities in query exceeded maximum limit' exception when dealing with moderately sophisticated data models with multiple or nested relationships. Another situation whe...
Implementation dependency management
CRM Portals implementations are a combination of CRM data and CRM schema, where the CRM data and schema have quite a diverse set of dependencies upon themselves and each other.
It becomes a very big challenge to understand all the dependencies and interrelationships between the data an...
Add Portals as a new 'product' to CRM Roadmap site to find information more easily
CRM Portals should be its own product on the Dynamics CRM Roadmap site so that we can more easily find and filter on information regarding upcoming and released features about CRM Portals. Having it mixed in within the generic CRM Online produ...
Entity Permissions should be assignable to specific features and not apply globally
Entity Permissions currently work in a way that all entity permission records that apply to a given entity and the logged in contact's web role are evaluated when operating on a record. This scheme falls apart once you have hundreds of entity permissions, because you can't tell what ...
Add a Custom CSS field to Entity Form and Web Form Step
The web page entity has both a Custom JavaScript and a Custom CSS field for outputting inline JavaScript and CSS on the web page. However, the Entity Form and Web Form Step entities only have a Custom JavaScript field.
I would like to see a Custom CSS field also added to the Entit...
Ability to have metadata records conditionally apply to Entity Forms and Web Forms
Web applications with business logic need the ability to dynamically control rules that apply to fields in a form. Common such needs are dynamically controlling when a validator will be applicable to a field as well as the visibility of a field. The most common examples are needing&n...
Support multiple modes for a single Entity Form
Entity Forms currently have the modes of Insert, Edit, and ReadOnly. This results in a lot of duplication of Entity Forms and related metadata records because data-oriented applications need to perform all 3 actions on the data being managed. It takes 3 times more effort to create applica...
Unify Entity Forms and Web Forms (i.e. get rid of Web Form Steps)
Entity Forms and Web Forms have a lot of overlapping concepts, this is a historical artifact of Web Forms having been implemented prior to Entity Forms. A Web Form Step is essentially an Entity Form, and they have a very high overlap in fields and related records (e.g. metadata).
Web F...