PL 400: Configure Forms (Create model-driven apps)

Forms are an essential component of any business application or web application, as it allows the user to interact with the computer. In simple words, a form is the shape, visual form or configuration of an object that provides a component-based representation of a GUI window. Similarly, in model-driven apps, forms provide the user interface that the organization uses to interact with the data it needs to perform its work and includes a set of data entry columns for a given table.


There are several types of Forms:

Main : These Forms provide the main user interface for interacting with entity data.
Quick Create: These Forms provide a basic form optimized for creating new records.
Quick View: These Forms appear within the main form to display additional data for a record that is referenced by a lookup field in the Form.
Card: Used in views for unified interface apps.

According to Microsoft:
Forms provide a structure way to represent the data when it is rendered for interaction with user.



Forms abstract the forms creator from the exact rendering specifics required to transform the form definition we create for the user's device size and capabilities.

Unified Interface is the current framework that renders the form definition for the user.

In model-driven apps, forms are organized into a header, body, and footer, each of which includes form elements such as columns. The body of the form is structured with areas called tabs that contain sections. Tabs and sections can be configured to support columns of form elements giving the control more structure.

Configure the Main Form :
  • Sign in to Power Apps.
  • Expand Data, select Tables,
  •  Select the table that you want, and then select the Forms tab.
  • To create a new main form, on the toolbar select Add form > Main Form. -OR- To edit an existing main form, select any form with the Type of Main.
Configure the quick create forms:
  • Sign in to Power Apps.
  • Expand Data, select Tables, select the table that you want, and then select the Forms tab.
  • On the toolbar, select Add form > Quick Create Form.
  • In the form designer drag any columns from the Column Explorer into the sections on the form.
  • When you are finished, select Save.
  • Select Publish to see the new form in the application.
Configure quick view forms:
  • Sign in to Power Apps.
  • Expand Data, select Tables, select the table that you want, and then select the Forms tab.
  • On the toolbar, select Add form > Quick View Form.
  • In the Form panel, enter a Display Name and Description to differentiate this quick view form from any others.
  • In the form designer drag any columns from the Columns Explorer into the section on the form.
  • To save the form select Save.
  • Select Publish to see the new form in the application.
Configure the Card:
  • Sign in to Power Apps.
  • Expand Data, select the table you want, and then select the Views tab.
  • Select the view that you want, and then on the view designer toolbar, select Switch to classic.
  • Select Custom Controls from the Common Tasks pane.
  • Select Add Control, from the list of controls select Read Only Grid, and then select Add. 
  • From the Read Only Grid properties page configure the following properties, and then select OK.
    • Card Form. Select the pencil icon Edit control properties. and then select the card form you want to display in the view. By default, the primary table associated with the view is already selected, but you can change it.
    • Reflow behavior. If you want to change whether the card form displays when resized, select the pencil icon Edit control properties.. More information: Allow grid to reflow into list
  • Select the client types, Web, Phone, or Tablet, where you want the Read Only Grid control to display.
  • Select OK to close the Custom Controls properties page.
  • On the classic view designer toolbar, select Save and Close.
Important Points :
  • Each table must have a designated fallback form. This is the form that all users would see if they do not have a security role assigned that matches your role tailored forms.
  • Only Main forms can be assigned to security roles.
  • When a user has access to multiple forms, a form selector will be available near the top of the form. If a user has access to only a single form for a given table, there will be no form selector visible.
  • We can designate a main form as inactive. This will make it not visible to all users, regardless of security roles. 


Comments

Post a Comment

Popular posts from this blog

Exploring the Differences: Managed vs. Unmanaged Solutions in Dynamics CRM/Dataverse

Image
In Dynamics CRM/Dataverse, solutions are central to Application Lifecycle Management (ALM) , providing a structured way to manage, package, and distribute customizations across environments. Microsoft uses solutions to transfer apps and customizations by exporting them from one Dataverse environment and importing them into another.  Each solution is authored and maintained by a publisher and includes components like Power Apps (canvas and model-driven), flows, entities, forms, connectors, web resources, and configurations—excluding business data. Solutions streamline ALM practices within Microsoft Power Platform. In Dynamics CRM/Dataverse, there are two types of solutions: Managed and Unmanaged . When planning an implementation, it’s important to understand the advantages and disadvantages of each to make an informed decision. Let’s explore both types to determine the best approach for development and deployment. In Dynamics 365 CRM, a managed solution is a fully packaged solution ...
Read more

PCF vs. Web Resources: Choosing the Right Extensibility Tool for Dataverse

Image
Extensibility refers to the ability to be extended or augmented beyond the default capabilities of the platform. This involves customization but also includes more advanced techniques, such as coding, integration with external services, and the use of custom components. In the context of Power Platform and Dynamics CRM, the term "extend behavior" refers to the ability to customize and extend the functionality of the platform to meet specific business needs. Extensibility often requires technical skills, such as coding in JavaScript, C#, or using tools like Azure Logic Apps and Power Automate for complex integrations. Customization  is a subset of extensibility. Customization involves configuring and modifying existing elements within the platform to suit specific business needs. Extensibility, on the other hand, covers a wide range of functions and techniques, including customization and more advanced development and integration tasks, to extend the capabilities of the Power ...
Read more

Effective Strategies for Debugging Plugins in Dynamics CRM

Image
In a recent interview, I was asked about debugging plugins in Dynamics CRM. The interviewer specifically wanted to know my approach to plugin debugging. In response, I mentioned using the Plugin Registration Tool profiler. However, I later realized there are multiple methods to debug plugins in Dynamics CRM/Dataverse, each essential for efficient troubleshooting. Debugging plays a crucial role in development, and having a solid understanding of various debugging approaches can help streamline issue resolution in Dynamics 365. Here, I'll explore different techniques for debugging plugin code. There are below options to use in the plugin in Dynamics CRM/Dataverse ITracingService : In Dynamics CRM plugin development, ITracingService is a service provided within the plugin's execution context that logs information for tracing and debugging. It allows developers to capture real-time. Plugin Profiler : A plugin profiler in Dynamics CRM (or Dataverse) is a debugging tool in the Plugi...
Read more