XRM.WebForm Pro solution contains all features of XRM.WebForm (Basic) version. Everything that is supported in basic version is also available in Pro version. However the updated version will let users control the published web forms a lot better.
Advanced Xrm.WebForm version with many new features is out!
With XRM.WebForm PRO, following types of WebForm Field are introduced:
- File Upload
- Validation Message
Slug feature is delivered with the purpose to enable setting default values of WebForm Fields using URL of the WebForm. Slug represents unique readable Id/Name of the WebForm Field that can be embedded within the URL of the WebForm as a query parameter. If a WebForm Field 1 has slug value set to “slug1” and if the WebForm is loaded with the query parameter “slug1=value1”, then the default value of WebForm Field1 will be set to “value1”, when the WebForm loads. The purpose of this feature is to dynamically set the default value, depending on the context in which the WebForm loads, as it can be injected on the WebForm via URL. The major usage of this would be to pass some information to hidden fields on the WebForm, such as Id or Name (if the WebForm visitor is not anonymous) or even IP address of the WebForm visitor who submits the WebForm. Also, it allows certain customizations on the WebForm depending on the information about the visitor. For instance, “Country” dropdown field on the WebForm can be set to specific default value based on the IP address of the WebForm visitor. These two are just small illustrations of numerous use cases of this powerful feature.
Related Entity Lists are PRO feature that enables exposing CRM data to the WebForm. Records of any entity which is a relationship with the target entity of the WebForm can be exposed to the WebForm and WebForm visitor can select some of them. When the WebForm is submitted and the record created, selected records of the related entity will be associated with the newly created record. This is powerful feature allowing WebForm editors to manage data visible on their website through the CRM and it allows creation of richer WebForms which collect incomparably wider set of data about WebForm visitors. The feature is very customizable, as it will be explained in this section of the guide, allowing WebForm editor to select records or specify conditions, to specify the set of fields of those records, to choose on its appearance on the WebForm and whether the data will be pulled automatically from CRM. Potential use case scenario is the WebForm having a checkbox list with all company’s products in which the WebForm visitor selects products they are interested in. Another case is the WebForm containing the table with company’s offices and the WebForm visitor chooses in which office they will follow up on the only application. There are numerous other examples of Related Entity Lists use cases, all of them empowering businesses to gather wider and more complex information from their website about their leads and customers and storing them in a very easy and systematic way in CRM.
Sub Form feature of a WebForm allows users to add child WebForms to the main WebForm. With the use of a Sub Form, several records of related entity can be created alongside the creation of the main record, when the WebForm submission happens. Besides creating the records of related entity, they are also associated to the main record automatically. To illustrate the use of Sub Forms, let’s see following example: WebForm author can create WebForm which has target entity set to Contact and then create another WebForm which has target entity set to Account entity. The author can add Sub Form to Account WebForm and set Sub Form’s WebForm to previously created Contact Web Form. It can define that maximum number of Contact records that can be created using that Sub form is 5 and minimum is 2. When the author deploys Account WebForm, it will contain the list of WebForm Fields of the Account (as expected) and Sub Form section containing several Contact WebForms. When the WebForm visitor fills this Account WebForm, he needs to add at least 2 contacts (fill at least 2 Contact WebForms) and he can add maximally 5 contacts. When the visitor submits the WebForm, one account record and 2-5 contacts will be created in the CRM. Besides the creation, all created contact records will be associated to the account record. This was just a quick illustration of how Sub Forms work and in further text, all features of Sub Forms will be explained in detail.