Basic Forms / Entity Forms in MS Power Apps Portals.

Entity Forms and Basic Forms both are same recently, Responding to customer feedback and data from user research, effective November 2020 Microsoft updated some terminology in Common Data Service to be more intuitive and make its usage more productive.

A data-driven configuration to allow end users to add a form to collect data in the portal without the need for a developer to surface the form in the portal, basic forms are created in Microsoft Dataverse and then placed into webpages in the portal or used in conjunction with subgrids and lists to build out complete web applications.

How to Create Basic Form?

• An Basic Form must be associated with a webpage for a given website for the form to be viewable within the site.
• The Connection table subgrids aren’t supported in basic forms. If you add a Connection table subgrid to the form using Form designer, error messages are displayed when you render the form on the portal and use the Connection table.
• Duplicate fields, multi-select option set, custom controls, Party List fields and business rules aren’t supported in basic forms.
• Image attributes, file attributes and table images aren’t supported in basic forms, advanced forms or when using liquid template tags, such as fetchxl.
• Business rules and client API can enable locked fields on a read-only form.
• If you create a basic form in the Insert mode, you can’t change a button’s alignment or place an action button above the basic form.
• If you render a lookup control as a dropdown list on the form, the related records filter does not work.

Terminology updates in Microsoft Power Platform

Legacy term	Current term
Entity, entities	Table, tables
Field, fields Attribute, attributes	Column, columns
Record, records	Row, rows
Option set, multi select option sets Picklist, picklists	Choice, choices
Two Options	Yes/No

 Note:

These terminology updates aren’t applicable to any APIs or messages in the Dataverse web services. For example, the names of the CreateEntityRequest and CreateAttributeRequest won’t change.

Web Templates in MS Power Apps Portals

How to Create WebPages, Web Templates, and Page Templates in MS Power Apps Portals.

How to create custom portals websites using power makers.

Customize content by using content snippets.

Site settings for the Web API in MS Power Apps Portals

You must enable the site setting to enable the portals Web API for your portal. Also, you can configure the field-level Web API that determines the table fields that can or can’t be modified with the portals Web API.

Note: that configuration entities (those prefixed with adx) are not available for Portals Web Api.

Site setting name	Description
Webapi/<table name>/enabled	Enables or disables the Web API for <table name>. Default: False Valid values: True, False
Webapi/<table name>/fields	Defines the comma-separated list of attributes that can be modified with the Web API. Possible values: – All attributes: * – Specific attributes: attr1,attr2,attr3 Note: The value must be either an asterisk (*) or a comma-separated list of field names. Important: This is a mandatory site setting. When this setting is missing, you’ll see the error “No fields defined for this entity.”
Webapi/error/innererror	Enables or disables InnerError. Default: False Valid values: True, False

For example, to expose the Web API for the Account table where authenticated users are allowed to perform create, update, and delete operations on this entity, the site settings are shown in the below Images.

Go to Portal Management App:

For Error Reporting:

Enable the Entity:

Specify the Fields (I choose all fields, by setting the value to *):

How to use session storage set item and get items in Web/ Advanced forms of Ms power apps portals

Scenario: In Register Web/Advanced Form what ever the data given in First Step fields such as First name, Middle name and Last name need to set the same values in second step fields of Cadet first name , Cadet middle name and Cadet last name fields.

Web/Advanced Forms

Step 1: Get the Schema names of First name, Middle name, Last name and Cadet first name , Cadet middle name, Cadet last name fields.

Step 2: Write jQuery for Web/Advanced Form First Step as below.

$(document).ready(function() {
    setsessionstorage();
    $("#new_firstname").change(function() {
        setsessionstorage();
    });
    $("#new_middlename").change(function() {
        setsessionstorage();
    });
    $("#new_lastname").change(function() {
        setsessionstorage();
    });

    function setsessionstorage() {
        sessionStorage.setItem('new_firstname', $('#new_firstname').val());
        sessionStorage.setItem('new_middlename', $('#new_middlename').val());
        sessionStorage.setItem('new_nameofthecadet', $('#new_lastname').val());
    }
});

Step 3:  Paste the code in respective Advanced / Web Form First Step and save the records shown in below image.

Step 4: Write jQuery for Web/Advanced Form Second Step as below.

$(document).ready(function () {
   if (sessionStorage.getItem('new_firstname') !== undefined &&
        sessionStorage.getItem('new_firstname') !== null &&
        sessionStorage.getItem('new_firstname') !== "") {
        $('#new_cadetfirstnameinacertificate').val(sessionStorage.getItem('new_firstname'));
        $('#new_cadetmiddlenameinacertificate').val(sessionStorage.getItem('new_middlename'));
        $('#new_cadetlastnameinacertificate').val(sessionStorage.getItem('new_lastname'));    
    }
	});

Step 5: Paste the code in respective Advanced / Web Form Second Step and save the records shown in below image.

Step 6: Clear the Portal Server Side Cache.

Step 7: Now Check your functionality is working as expected or not.

How to Validate Name Attribute using jQuery in ms crm power apps portals.

Step 1: Get schema name of first name.

Step 2: Write jQuery as shown below.

$(document).ready(function() {
    $("#new_name").change(function() {
        CheckcadetFirstName();
    });

    function CheckcadetFirstName($firstName) {
        var charRegExp = /^[a-zA-Z -]+$/;
        //  Get the firstName Address
        var cadetFirstName = $("#new_name").val();
        if (cadetFirstName != null && cadetFirstName != "") { // Check condition 
            if (cadetFirstName.search(charRegExp) != 0) {
                // Display Alert     
                alert("Please enter a valid first name.");
                // Clear out firstName field & set focus
                $("#new_name").val(""); // Clear the Value of First Name
                $("#new_name").focus(); // Set focus on First name
            }
        }
    }
});

Step 4: Paste the code in respective Basic / Entity Form and save the records shown in below image.

Step 5: Clear the Portal Server Side Cache.

Step 6: Now Check your functionality is working as expected or not.

 Hope it helps to you guys, if you struck anywhere add your comments in comment box section will help you out to fix the issue.

How to Enable and Disable Buttons using jQuery in Ms power apps portals

Scenario: If Name attribute contains data enable Submit Button else Disable.

Step 1: Get the Id of Submit button through inspecting the element(F12) as shown below.

Step 2: Get Schema name of Name

Step 3: Write jQuery as below.

$(document).ready(function() {
    enableDisable();
    
    $("#new_name").change(function() {
        enableDisable();
    });

    function enableDisable() {
        var name = $("#new_name").val();
        if (name !== null && name !== "" && name !== undefined) {
            $("#InsertButton").prop('disabled', false);
        } else {
            $("#InsertButton").prop('disabled', true);
        }
    }
});

Step 4: Paste the code in respective Basic / Entity Form and save the records shown in below image.

Step 5: Clear the Portal Server Side Cache.

Step 6: Now Check your functionality is working as expected or not.

If Name field Doesn’t contains data Submit button should be in disable mode.

If Name field contains data Submit button should be in Enable mode.

Hence, Both conditions are working as expected.