Dynamics Forms: Create/Edit System and Web Forms

Created by Kevin Schmidt - HCPro, Modified on Thu, 9 Oct at 3:21 AM by Kevin Schmidt - HCPro

This document outlines the process of creating a new form in Dynamics 365. 


Step 1. Collect survey form requirements (questions, format, page breakdown, attachment requirements, etc.)

Step 2. In Dynamics 365 QA, go to Settings à Advanced Settings à Settings drop-down à Solutions

Graphical user interface, application, website

Description automatically generated


Step 4. Select the base solution name where the form will be created.

AHIMA_Customizations contains all general AMS forms.

AHIMA_CEP_Certification contains all ACEP-related forms.

AHIMA_Donations contains all Foundation Donation forms.

AHIMA_Events contains all Meeting/Events forms.

AHIMA_Sales contains all Sales forms.

Graphical user interface, text, application

Description automatically generated


Step 5. On left-hand navigation, click the dropdown arrow next to the entity that you would like to create the web form (i.e. Volunteer Submissions)

Step 6. Click on FORMS and select an existing form to edit or create a new form.

**TIP: New forms created will need to be “saved as” under a new form name (spacing OK; this form name will serve as your form schema name for the purposes of linking it to a web form. 

 

Graphical user interface, text, application, email

Description automatically generated

**TIP: add new entity form for each new web form page.

 



ADD COMPONENTS TO AN ENTITY FORM 

Components are essentially ways that you can compartmentalize information on an entity form, present information to front-end users, and many more customizable features such as:

  • Sections
  • Tabs
  • Reference Panels
  • Sub-Grids*
  • Spacer
  • Quick View Form
  • Web Resource
  • iFrame
  • Timeline (activities, posts, notes)
  • Social Insights
  • Timer

Graphical user interface, text, application, email

Description automatically generated

 

Step 1. To add a new component to the overall layout of your entity form go to the INSERT tab.


Graphical user interface, text, website

Description automatically generated

Graphical user interface, text

Description automatically generated

 



ADD FIELDS TO AN ENTITY FORM

**TIP: Make note of your entity name (schema) to link to a web form. 

Graphical user interface, application

Description automatically generated


Step 1. Go to the base entity and click on Fields, then click New to add a new field option. Each new field option is a new form question (or statement).

Step 2. Complete the General tab in the new field record


Graphical user interface, text, application, email

Description automatically generated

Step 3. Enter DISPLAY NAME (name will automatically populate)

Step 4. Select FIELD REQUIREMENT options (Optional, Business Recommended, Business Required)

Step 5. Modify TYPE (e.g., Single Line of Text, Multiples Line of Text, Multiple Choice, etc.)

Step 6. Click save and close.

TIP: Save and close the Form record to refresh.

Step 7. Open the Form (again). The newly created FIELD should now be available in the active lists of fields (right-hand side panel).

Step 8. In the Form, go to the INSERT tab and add a new form component (e.g. Column, Section).

Step 9. Edit FIELDS in the form to customize components.

 



CREATE WEB FORM

Step 1. Click on any existing web form in the WEB FORMS view.

Step 2. Click + NEW to create new web form.

Step 3. Ensure the Web Form is created in AMS_Web Form


Graphical user interface

Description automatically generated with medium confidence


Step 4. Complete the General Tab

  1. Name = For web forms, save the web form name starting with “web_” (do not include spacing)
  2. Chained Form = Yes/No (specific record goods to be passed along) Yes = linked forms that are related.
  3. System Form Name = This is your entity form name (for each entity form name you will have a web form). You can access your entity form name by clicking on MANAGE PROPERTIES within the Entity Form in Solutions. Spacing OK.
  4. Parent Entity Type = Parent Entity Name and Related Entity Attribute (schema name of the Form entity) fields in web form are used to call back account/contact data. These fields are typically used for fields that the user will want to update (i.e. member profile).
  5. Entity Name = Copy the name of you Form entity (or schema). Go to the main Form entity and in the general tab is the display name. The Name field is the schema name. This will be needed to complete the ENTITY NAME in your new web form.
  6. Related Entity Attribute = Parent Entity Name and Related Entity Attribute (schema name of the Form entity) fields in web form are used to call back account/contact data. These fields are typically used for fields that the user will want to update (i.e. member profile).


Step 5. Complete the Display Options Tab

  1. Query by Example (Web Form Search) = Mark “Is QBE?”
  2. Additional Display Content
    • Web Form Header (images, page headers)
    • Web Form Footer
    • Form javascript (styles)
  3. OPTIONAL: Conditional logic can be done through javascript OR custom callout (dev work)


Step 6. Complete the Navigation Options Tab

  1. Next Navigation*

*Control Navigation on the Form

0 - None = save button

1 – Specific Form = (complete Next Web Form)

2 – Specific Category

3 – Save and Redirect = saves the page and redirects user to another web page

4 – Checkout

5 – Form Action = multiple buttons at bottom of the page (e.g. next, Cancel, Back)

6 – Specific Web Product

7 – Cart

  1. Redirect URL (Applies to #3 only)
  2. Next Web Form (Applies to #1 only)
  3. Web Product (Applies to #6)
  4. Next Category (Applies to #2 only)
  5. Chained Form (Yes/No) - (specific record goods to be passed along) Yes = linked forms that are related.


TIP: For conditional forms, the web form should include redirect to next form.



Create New Web Form Element Extensions

  • Linked to Fields or Sub-grids that are added to Entity Form
  • Name = name of the field (schema name) or subgrid that you want to control with the element exception (e.g. make it required)

Step 1. To create a new ELEMENT EXTENSION, click on + new web form element extension

 

Graphical user interface, text, application

Description automatically generated

 

Step 2. Complete the General Tab

  1. Name = entity form schema name
  2. Web Form (LOCKED)
  3. Next Web Form (Add/Edit Web Form) = autopopulates if a new element extension is added via the original web form

Step 3. Complete the SubGrid Setup Tab

  1. Command Types Option Sets:
    • Add: adding a new record/product to the record (e.g. you have subgrids of course and want to add new course)
    • Add/Update: add or update and records/products on subgrid
    • Update: update any record/products in grid (modify existing ones)
    • Add/Update/Delete: DO NOT USE (cannot actually delete records/products from subgrid)
    • Add to Cart – Invoice Only: invoices only that are open. Option to add invoice to cart.
    • Pay Invoice: Adds button to direct user to make a payment.
    • Reprint – Invoice Only: Adds button for user to reprint invoice that is closed.
    • Navigation: takes you into the record.
    • Custom Callout: writing code
  2. Custom Callout2 = ??  

Step 4. Complete the Field Setup tab

LOOKUP FIELD OPTIONS

  1. Allow Add New = Yes/No
  2. Lookup Data Behavior = Display as Search / Display as Dropdown

                      FIELD OPTIONS

  1. Render as File Upload = Yes/No
  2. Validator Type = None/Required/Custom/One of Many/Any of Last

                      DISPLAY FORMATTING

  1. Telephone
  2. Money
  3. Url
  4. Email


TIP: Element extension may be required for fields that are displaying as drop-down in place of displaying data. 

 


Add SubGrid (if needed) 

Subgrids are used as a means to display data table on web form. 

  • Add new section – one column
  • Select what accounts/records you want to see – based on available system views. The record type needs to be related entity.

 

(click “related” or the ellipsis to expand more tabs)

 

  Add Remove (Deactivate) Functionality on Subgrid

  • Can deactivate files from Subgrid through sub-grid action  

  • Name of sub grid = Subgrid name  

  • Action = deactivate 

  • Entity 

  • Button order = 1 or 2  

  • Tool Tip (hoover over language) – e.g., remove the file 

  • Icon – what icon appears on the form for Subgrid action. Look under available icons (enter “clear” or “close” to get X) 


Form Actions 

Add new Form Actions to Web Form record for every new button you want to add to the page.

       To create a new FORM ACTION, click on + new Dynamic form action.

Graphical user interface, application

Description automatically generated

              General tab

  1. Name = name of the actual button on the page
  2. Action = option sets below
    1. Cart = go to cart
    2. Checkout = go to checkout
    3. Custom callout = custom code
    4. Navigate = push to next page (provide next web form)
    5. Redirect = to a URL (provide redirect URL field)
    6. Save and redirect = save changes and to a URL (provide redirect URL field)
    7. Save a reroute = save and go to new web form (provide next web form)
  3. Button Order LTR (left to right) = the order in which the button will be displayed.

OnClick JavaScript - ???

 

SAMPLE:

Graphical user interface, application, email

Description automatically generated

 

TIP: OBJECTOBJECT errors are thrown out typically when there is an error in the SYSTEM FORM NAME or ENTITY NAME


 Web Form w/ Search Functionality

  1. Web form should be marked as QBELD (Query by example large dataset)
  2. QBELD should be included in hash location (" #/qbeld/webformname " ) 
  3. System Form 
    • 1st Tab: Add search by fields
    • 2nd Tab: Add subgrid of what you want to display post-search  

Sample File Attachment Entity Form and Web Form

Entity Form Components

Table

Description automatically generated

Component:

Graphical user interface, application

Description automatically generated

Field

Graphical user interface, text, email

Description automatically generated

Field Properties

Graphical user interface, application

Description automatically generated

Field Details

Graphical user interface, application

Description automatically generated

 

SAMPLE CONFIGURE ELEMENT EXTENSION TO SUPPORT FILE UPLOAD IN WEB FORM

Create new web form element extension

General tab

  1. Name = entity form field schema name
  2. Web Form (LOCKED)
  3. Add/Edtit Web Form (auto-populates if added directly from the original web form record)

SubGrip Setup tab

  1. Command Type = x-Read Only

Field Setup 

  1. Allow Add New = No
  2. Lookup Data Behavior = Display as Search
  3. Render as File Upload = Yes
  4. Validator Type = None
  5. Display Formatting = (LEAVE THIS FIELD BLANK)

 

Graphical user interface, text, application, email

Description automatically generated

Graphical user interface, text, application, email

Description automatically generated

Graphical user interface, text, application, email

Description automatically generated

 

                                                

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article