1. Adxstudio Portals Training
Entity Forms

2. Displaying Forms CRM Forms Creating an Entity Form Entity Form Options
Metadata and Localization
What are CRM forms and why do we want to render them on the portal?
Let’s create a simple Entity Form for the common “Contact Us” scenario
A look at some of the various options available for entity forms, extending their OOB functionality
Metadata allows for further configuration of fields on Entity Forms. Localization is necessary for multilingual portals

3. Why Forms? Lead Generation Profile Management Data Entry
Custom Web Apps
Surveys

4. Forms CRM Forms Managed Forms Adxstudio Entity Forms ASP.NET Web Forms
Adxstudio Web Forms!

5. Entity Forms Surfacing CRM Forms
Allow users to define entity forms and custom logic within the CRM Data entry forms within Adxstudio Portals No coding required Can use existing CRM forms on the Portal
A basic way to display information about and allow CRUD operations against CRM entities on the portal in an arbitrary fashion

6. Displaying CRM Forms

7. Creating a Lead-Generating Contact Us
Typical Scenario: A Contact Us
All that’s needed is a form for the lead entity, with the fields you wish to collect on the Portal
Create a Web Page and Entity Form to surface your CRM form

8. CRM Entity Form Feature Matrix
Supported?
All CRM Field Types
Yes
All CRM Field Validation Rules
Multiple Column Layouts
Inline Web Resources
CRM Label Language Translations
Sub-Grids
Yes (configure with metadata)
Header & Footer
Roadmap
Notes
IFRAMEs No
CRM Form Scripting

9. Entity Form Structure Web Page Entity Form Attribute Metadata
Sub-grid Metadata
Notes Metadata

10. Form Definition Attributes
Entity Name
Name of the Entity that we are displaying on the portal
Mode
Defines the write action if any that the form is preforming:
Insert: Create a new record
Edit: Change an existing record
ReadOnly: Display an existing record
Form Name/Tab Name
Defines the Form (and if applicable, the Tab) that will be displayed
Record Source Type
Defines the record that will be loaded in the case of edit or ReadOnly mode:
Query String
Current Portal User
Record Associated to Current Portal User
Enable Entity Permissions
If set to true this form will respect Entity Permissions

11. Entity Form Additional Options
Auto Generate Steps from Tabs
Associate Current Portal User (Insert Only)
Attachment
Custom JavaScript
Set Entity Reference
Notes

12. Entity Form Metadata
Contains additional behavior logic to extend functionality of CRM form fields
Type
Attribute
Section
Tab
Subgrid

13. Entity Form Metadata Attribute Type
Prepopulate Field
Set Value on Save
Validation
Survey Control Styles

14. Subgrids
Subgrids added to a CRM form will show up on the portal just like any other control
Respects all settings on the grid in CRM
Will be read-only without metadata
To add actions such as Edit, add a metadata record for the Subgrid to the Entity Form (type: Subgrid)

15. Subgrid Action Configuration
Actions can be configured such as Create, View, Edit, Delete, Run Workflow
In order to configure these actions for subgrids, you must add a metadata record for each subgrid on the form
Set the subgrid name, then add actions for each of the operations you wish to be available on the form
Create, Edit, Delete require Entity Forms to be in place
All Actions require the appropriate permissions

16. Subgrid Configuration

17. Notes Work the same way as Subgrids Require permissions to be in place
Read-Only by default
Additional functionality requires metadata configuration

18. Localization Requires a Multilingual Website to be in place
Install language packs and supply label translations
Create a system user account for each language to be surfaced on the portal
Configure Web.config
Modify the Page Template for Entity Form