Power Apps: Forms, Variables, & Collections

By Ashwin Venugopal -

 




Forms

Forms are set up in a manner akin to galleries, utilizing a drag and drop interface for their creation and configuration. We have the ability to change the arrangement of items in our form (referred to as data cards) by simply dragging and dropping within the interface. Additionally, we can select various options for each of our fields along with their visibility and editability through the properties. If we prefer not to allow our users to input data, we can also opt to remove fields (data cards) from our form.

Just like Galleries, we have significant design flexibility and can utilize the properties of individual controls in our form to modify elements such as color and behavior. By default, forms do not allow users to submit data, this functionality must be implemented manually by the developer. Depending on your desired form behavior, there are various methods to achieve this, with the most common being a clickable button on the canvas that sends the data entered into the form to the database, thereby creating a new record.

Start by placing a button onto your canvas. Next, utilize the OnSelect property of the button to include the formula SubmitForm(Form1). By using the OnSelect property, the formula will execute every time the button is clicked or selected by the user. The SubmitForm formula is a standard Power Apps formula that is designed to send data to a specified data source provided in the function's parameters.

Power Apps offers more sophisticated methods for generating new records in data sources through the Patch function. This function provides greater control and flexibility regarding the submission of your data.

Variables & Collections

Creating Variables

A phone book can be viewed as a directory for storing contacts, allowing us to add, delete, or update the names and numbers of individuals. Whenever we consult this phone book, we have access to the most current contacts available to us. A variety of data types can be held in variables, including colors, numbers, table records, and strings. Additionally, these values can be modified within our application by applying the same formula while altering the value.

Using Variables

We can reference any variable we’ve created within formulas by using its name. Variables are stored in a local context, which means they are established and removed based on the app's workflow. When the application is closed, the variables are erased and will be set up again the next time the app is launched or accessed, and this applies to collections as well.

Collections

A collection serves as a local table that exists in the environment where the application operates. They enable us to set up and maintain data in a table format, which can be accessed similarly to a variable by using the collection's name. In the formula bar, we can utilize Collect, specify a name for our collection, and then designate a column name followed by the value we wish to insert into that table or collection. We can view our collection inside the Power Apps Studio under the Variables tab in the App Authoring Menu along with any other variables that exist in our app.

Conclusion

We have successfully learnt about forms as well as variables and collections.

























Comments

Post a Comment

Popular posts from this blog

Information Protection Scanner: Resolve Issues with Information Protection Scanner Deployment

By Ashwin Venugopal -
Image
  About If you are experiencing problems with the Microsoft Purview Information Protection scanner, check the health of your deployment by utilizing the Start-ScannerDiagnosticsPowerShell cmdlet to start the scanner diagnostic tool. The diagnostics tool checks the following details and then creates a log files with the results: Whether the database is up to date. Whether network URLs are accessible. Whether there's a valid authentication token and policy can be acquired. Whether the profile is defined in the Azure portal. Whether offline/online configuration exists and can be acquired. Whether the rules configured are valid.  The Start-ScannerDiagnostics command does not perform a comprehensive check of prerequisites. If you encounter problems with the scanner, you need to verify that your system meets the scanner's requirements, and that your scanner's configuration and installation are finished.  Verify Scanning Details Per Scanner Node and Repository Run the Get-ScanSt...
Read more

How AMI Store & Restore Works?

By Ashwin Venugopal -
Image
  CreateStoreImageTask The CreateStoreImageTask API stores an AMI as a single object in an S3 bucket. The API initiates a task that collects all the data from the AMI and its associated snapshots, subsequently using an S3 multipart upload to store this data in an S3 object. It gathers all elements of the AMI, including most of the non-Region-specific metadata and all EBS snapshots included in the AMI, and consolidates them into a single object in S3. During the upload process, the data is compressed to minimize the space utilized in S3, which means that the S3 object could be smaller than the total sizes of the snapshots in the AMI. If the account making this API call has access to AMI and snapshot tags, they will be retained. The S3 object shares the same ID as the AMI, except it has a .bin extension. Additionally, the S3 metadata tags for the object include the AMI name, AMI description, AMI registration date, AMI owner account, and a timestamp indicating when the store operation...
Read more

Create A Store Image Task

By Ashwin Venugopal -
Image
  Introduction When you save an AMI in an S3 bucket, a task for storing the image is initiated. This store image task allows you to track the progress and result of the procedure. Securing your AMIs It is crucial to verify that the S3 bucket is set up with adequate security to protect the content of the AMI and that this security is upheld for the entire duration that the AMI objects are stored in the bucket. If this cannot be achieved, it is advisable to refrain from using these APIs. Make sure that public access to the S3 bucket is prohibited. It is suggested to activate Server-side encryption for the S3 buckets where you keep the AMIs, even though it’s not mandatory. When AMI snapshots are transferred to the S3 object, they are sent over TLS connections. It is possible to save AMIs that contain encrypted snapshots; however, the snapshots will be decrypted during the storing process. Identify the source AMI used to create a new Amazon EC2 AMI You can determine the AMI that was us...
Read more