Click to view full image

Adxstudio Portals delivers managed forms by rendering a form in an Adxstudio Portal based on a particular form or view customization defined on an entity in CRM. Within CRM, entities can be customized and forms and views can be modified or created depending on your requirements. Typically an entity consists of attributes that you would like to expose in a portal to allow users to provide values to create records in CRM. Generally we recommend creating a new form for use within the portal seperate from the main form(s) used within CRM to view the records. This provides the ability to ensure fields that should be exposed to the portal and those that should only be seen within CRM are maintained. Once an entity's form or view has been edited to suit your desired layout then a developer can add the CrmEntityFormView custom server control to a page template to surface the form in a web page within the website. The portal will render one or two column form layouts and for a saved query view it will render a single column layout. An end user can modify the form or view in CRM and the changes will be reflected in the website without the need for a developer to manually modify form fields in the website. See the developer's guide for CrmEntityFormView for information on adding the functionality to a particular web page in your site for gathering user data entry. Our starter portals contain several examples of managed forms. Please refer to the details of each starter portal in the Portal Applications Guide for more details.

For more information regarding the creation of entity forms and customizations in CRM please refer to the documentation on MSDN by visiting the following URL

Entity Support

The following entities are not supported for use with managed forms.

  • Product - This system entity requires an internal Query API method "PriceLevel.RetrieveByObject" that is not exposed by the SDK.
  • All activity type entities (email, phonecall, task, etc.) - These system entities contain a special “regarding” field that can be related to any type of record that has activities enabled that is problematic for the rendering engine.