1. Explain the error function in PowerApps?
When a record of a data source is modified, errors can occur. Network failures, insufficient permissions, and edit conflicts are all possibilities.
The Patch and other data functions do not return errors directly. They instead return the outcome of their operation. You can use the Errors function to get the details of any errors that occur after a data function has been completed. The [IsEmpty] function in the formula IsEmpty( Errors (...) ) can be used to check for errors. Using the Validate and DataSourceInfo functions, you can prevent some mistakes from occurring. For additional information on how to work with and avoid errors, see Working with Data Sources.
The Errors function returns
a table of errors with the columns listed below:
Record: The data source record that included the error. This field will be blank if the mistake occurred during the record creation process.
Column: If the issue can be traced back to a single column, here is the column that caused it. Otherwise, this will be left blank.
Message: An explanation of the problem. For the end-user, this error string can be displayed. Be aware that the data source may generate this message, which may be long and contain raw column names that the user may not understand.
Error: An error code that can be used in formulas to assist in the resolution of the problem. Syntax: Errors( DataSource [, Record ] )
DataSource: This is a must-have. The data source for which you'd like to get error messages.
Record: It is optional. You wish to return errors for a specific record. If this parameter is omitted, the function will return errors for the full data source.
2. In
PowerApps, how can I cache data?
To access this feature, go
to https://make.PowerApps.com > Apps > Other > Choose your Portal
application and click on Settings and then administration from the
drop-down menu. Select Portal Actions from the left menu and select Restart:
The website app service will be restarted, and the server-side cache will be
cleared.
3.
In PowerApps, how do I store an attachment?
Then, to enable attachments, you must:
Choose the forms to which you'd like to add attachments.
To open the data panel, click the Data box in the properties pane.
Find the Attachment field in the list of fields and turn it on.
Make a backup of your app and then publish it.
4. What's
the difference between PowerApps and Power Automate?
Microsoft PowerApps is
largely a form design tool, whereas Microsoft Power Automate is a workflow and
process automation program. They're individual items that can be mixed and
matched.
5.
How do you add components to a canvas app?
To get started, go to
PowerApps Studio.
Create a new canvas app or update an existing app with the code component to which you wish to add it.
Select Add (+) in the left pane, and then Get more components in the right pane.
Select the Code tab, then Import after selecting a component from the list.
6.
What is the purpose of the Power Apps Loading Spinner?
In PowerApps, the Loading
Spinner is an animated element that indicates when loading is underway. The
loading spinner will display if the data loading is taking too long. This means
that it aids in informing the user that the procedure is busy and that it may
take some time to appear.
In the Advanced tab, as well
as the Dropdown in the top left of the application, Microsoft offered a
property named "LoadingSpinner."
When you set the loading
spinner attribute to data, a loading spinner will appear anytime a user opens
the screen.
7. In
what programming language is PowerApps written in?
Microsoft Power Fx is a
low-level programming language that may be used to express logic throughout the
Microsoft Power Platform. It's the same language that's at the heart of today's
Microsoft PowerApps canvas programs, and it's inspired by Microsoft
Excel," said Greg Lindhorst, a Microsoft Principal Program Manager.
8. What
can I do to increase the performance of my PowerApps?
The performance of PowerApps
can e increased in the following ways:
Data connections should be limited: Don't use the same app to connect to more than 30 data sources. Apps require new users to sign in to each connection, thus each additional connector lengthens the time it takes for the program to load. When an app requests data from a source, each connector takes CPU resources, memory, and network bandwidth.
Reduce the number of controls used: Add no more than 500 controls to a single app. To render each control, Power Apps creates an HTML document object model. The more controls you include, the longer PowerApps takes to generate.
Improve the OnStart property's performance: If data doesn't change during the user session, use the ClearCollect function to cache it locally. Use the Concurrent function to load data sources at the same time, which can cut the time it takes for an app to load data in half.
Lookup data is cached: To prevent continually retrieving data from the source, use the Set function to cache data from lookup tables locally. If the data is unlikely to change during a session, this strategy improves performance.
Avoid screen-to-screen control reliance: Avoid screen-to-screen formula dependencies. You can exchange information between screens in some circumstances by using a global variable or collection.
Make use of delegation: Instead of retrieving data to the local device for processing, utilise functions that delegate data processing to the data source. When an app must analyse data locally, it requires significantly more processing power, memory, and network traffic, particularly if the dataset is huge.
Avoid using the same formula over and over again: Consider setting the formula once and then referencing the outcome of the first property in future ones if many properties run the same formula (especially if it's complicated).
DelayOutput should be enabled for all Text input controls: Set the DelayedOutput attribute of a Text input control to true if you have numerous formulas or rules that reference the value of that control. Only when a string of keystrokes has been entered in rapid succession will the Text attribute of that control be updated. The formulae or rules will not be executed as frequently, and the app's performance will improve.
9.
What are the drawbacks of using PowerApps?
PowerApps have the following limitations:
ü Under the Microsoft 365 umbrella, licensing is restricted.ü A convoluted licensing scheme.
ü It is costly.
ü Support for a variety of device sizes and screen orientations is limited.
ü The number of items allowed is limited.
ü The connector ecosystem's throughput limits is another limitation of PowerApps.
ü JavaScript isn't supported in PowerApps forms.
ü SharePoint as a back-end will function perfectly with attachment control. Attachment control will be disabled if custom SQL is used. Use OneDrive, SharePoint, or other cloud storage to store attachments and refer to them in PowerApps as a workaround.
10. What
Is A DataStore And How Does It Work? What Events Does It Now Support/No Longer
Support?
It's a statistics window
that can't be seen. If you wish to retrieve records from a desk without having
to show it, for example, you may pass for a statistics store. It no longer guides
clicked events, but now assists with deleting row (), inserting a row (),
retrieving row (), and updating row ().
It also supports the Item Error () event.
11. What
is a Combo Box? What distinguishes it from Drop-down?
In the PowerApps canvas software,
a combo box is a form of control. A Combo box control also allows you to search
for the items you want to select. Furthermore, because the search takes place
on the server, the performance of this search tool is unaffected. When looking
for items to pick, you can change the Layout options in the Data pane to show a
single data value, two values, or an image and two values (Person) for each
item.
Another sort of control
offered in PowerApps is a drop-down menu. This control saves screen space,
which is especially useful when the list has a lot of options.
Unless the user selects the
chevron to show more options, the control only takes up one line. A maximum of
500 things will be displayed in the control.
12. What
is the meaning of the Environment variable? How do you make one?
Environment variables are
produced in PowerApps for each environment and store the parameter keys and
values. Furthermore, these variables are used as input to a variety of other
application objects.
This method allows you to separate
the parameters from the consuming objects and alter the values within the same
environment or when migrating solutions to different environments.
The
following are some of the advantages of using environmental variables:
ü
While importing solutions to various environments, provide new parameter values.
ü Save settings for canvas apps and flows' data sources. You can, for example, keep SharePoint Online site and list parameters in environment variables, allowing you to connect to different sites and lists in different environments without having to change the apps or flows.
ü Continuous integration and continuous delivery (CI/CD) are enabled by SolutionPackager and DevOps tools.
ü The environment variables can be unpacked and saved in source control. You can also save different environment variables values files for the varied configurations required in various environments. The file matching to the environment where the solution will be imported can then be accepted by Solution Packager.
The
steps to create an environment variable in a solution are:
ª
Sign
in to Power Apps (make.powerapps.com) and then click Solutions from the left
pane.
ª Create a new solution or open the one you
want.
ª Select New > More from the command bar,
then the Environment variable.
ª Complete the following columns in the right
pane, then click Save:
ü
Display name: Give the environment variable a name.
ü Name: The unique name is produced automatically from the Display name, however, you can alter it if you want.
ü Data type: Decimal number, Text, JSON, Two options, Data source, or Secret are the possibilities available.
ü Current value: Also referred to as the value. This property is a part of the environment variable value table and is optional. Even if a default value is provided, if a value is available, it will be used. If you don't want to use the value in the next environment, remove it from your solution. Within the exported solution.zip file, the values are also divided into distinct JSON files that can be changed offline.
ü The default value: This column is not necessary and is part of the environment variable definition table. If there is no current value, the default value is used.
13. What
context does the power app/automate run in? In powerapps, how can you get
impersonation/elevated privileges?
Power apps run in the
context of the current user.
If your flow is triggered by
an automatic event, it will always operate in the context of a flow owner (Who
created the flow). Manually triggered flows, such as those that begin with a
button in a PowerApp, however, execute in the context of the person who clicks
the button.
Although there is no default
impersonation action, we can create two flows in which Flow A is called when a
power app button is pressed and passes HTTP request data to Flow B. This is
when we pass data that is critical to the business logic, lose all context
knowledge, and impersonate the user.
14. How
to export to excel in PowerApps?
Because there is no direct
function in PowerApps, we must use a flow to do this.
Create a button in PowerApps
and link it to a flow when the button is pressed.
As a parameter, pass JSON
data to the flow. To save the JSON data to excel in a SharePoint site, use the
create CSV and create file actions in the flow. To communicate back the URL of
our Excel file to Power App, use the react to power app action.
When the power app receives
the Excel link, it uses the download function to save the file.
15.
Explain concurrent function.
Multiple formulas are
evaluated at the same time using the Concurrent function. Multiple formulas are
usually evaluated by chaining them together with the ; operator, which
evaluates each one in turn. Users wait for less for the same outcome when the
app executes activities concurrently.
Syntax for concurrent
function: Concurrent( Formula1, Formula2 [, ...] )
Formula(s) – These are
required. Formulas for evaluating multiple variables at the same time. At least
two formulas must be provided.
We can utilise the
Concurrent function to run many formulas simultaneously. Instead of utilising
numerous formulas with a semicolon (;), you can use Concurrent to collect data
from many tables during Page Load, which will significantly shorten the overall
load time of the screen.
16.
Give an example of how to use the LookUp() and Filter() function. What
distinguishes it from Filter()?
The LookUp() function
locates the first record in a database that meets a formula's requirements.
LookUp() can be used to locate a single record that meets one or more criteria.
Filter(), on the other hand,
retrieves all records/items from a database that meet the criteria.
LookUp(Table*,
Formula [, ReductionFormula])
is the syntax for LookUp() function.
Example:
LookUp(Cake,
Flavour = “Chocolate”, Quantity)
Filter(Table*,
Formula1 [, Formula2, … ] ) is
the syntax for Filter() function.
Example:
Filter(cake,
“chocolate” in Lower(Flavour ));
17. What
is the difference between the PowerApps functions IsMatch, Match, and MatchAll?
The IsMatch method returns
True or False depending on whether a string matches a pattern, which is usually
done via a regular expression. The first record that matches a pattern is
returned by the Match function. For each match discovered, the MatchAll method
returns a table.
18. What
is the difference between an action and a trigger in MS-Flow?
Action: Changes guided by a User are referred to
as actions. For example, you can utilise an action to do SQL Database
operations such as lookup, update, and remove data. All actions will have
direct mappings to Swagger operations.
Trigger: Several connectors have triggers that can
be used to notify your app when certain events occur. Let's look at an FTP
connector with the OnUpdatedFile trigger as an example. You can create a Logic
App or a flow that listens for this trigger and takes action whenever it
occurs.
The trigger is divided
into two categories:
Polling Trigger: These triggers can check for new data by calling your service at a specific interval. When fresh data becomes available, your workflow instance will be restarted with the new data as input.
Push Trigger: These triggers can listen for data on an endpoint, which implies they'll wait for something to happen. The event triggers a fresh execution of your workflow instance whenever it occurs.
19. How
do I use the canvas components in my apps?
Components are reusable
building blocks for canvas apps, allowing app developers to design custom
controls and reuse them across several apps. Components can be exported and
imported between apps in different organisations. The Components are useful
since they allow you to create larger programs with similar control patterns.
For example, we may create a navigation control that can be used across
multiple screens in our program. When you update a component, your changes will
be reflected in all instances of the app.
Components ensure that
performance is upgraded or improved, as well as assisting in the
standardisation of the appearance and feel of PowerApps apps across an
enterprise. The input attributes of a component are also capable of receiving
values from the app, and the component can use these internally. Output
attributes, which are capable of giving output values to the app, are also
included in components.
20. In
PowerApps, how can Error Handling be implemented?
If there is a mistake while
sending the feedback, the app will display an appropriate message. This will
assist the salesman in determining what went wrong and how to proceed. The
Canvas App introduces the 'IfError' and 'isError' functions to handle errors
and display the relevant message.
To use these functions,
Formula-level error management must be enabled. Please follow the steps below
to enable Formula-level error management:
ª To begin, open the Canvas App and select File.
ª Go to Advanced Settings under Settings.
ª Enable Formula-level error management.
21.
Explain SaveData, LoadData and ClearData functions.
ü
The
SaveData function saves a collection under a name for later use.
ü The LoadData function reloads a collection
that was previously saved with the SaveData function. This function cannot be
used to load a collection from another source.
ü
ClearData
clears the storage associated with a given name, or all storage linked with the
application if no name is provided.
Syntax for SaveData,
LoadData and ClearData functions:
SaveData (
Collection, Name )
LoadData (
Collection, Name [, IgnoreNonexistentFile ])
Note:
The collection is a must. To
be stored or loaded, a collection must be made.
Name - This is required. The
storage's name. To store and load the same collection of data, the name must be
the same. Other programs or users do not have access to the namespace. Any of
the following characters must not appear in a name: *".?:\<>|/.
IgnoreNonexistent Optional
file. If the file doesn't already exist, a Boolean value indicates what to do.
To return an error, use false (the default), and to silence the error, use
true.
ClearData ( [Name] )
Name - This is an optional
field. SaveData already saved the name of the storage. All storage connected
with the app is wiped if the Name is not specified.
22. In
PowerApps, what does delegation mean?
The key to developing
efficient apps is to keep the amount of data on your device to a minimum. Maybe
you only need a few hundred records out of a million, or maybe a single
aggregate value might represent thousands of entries. When the expressiveness
of PowerApps formulas meets the requirement to reduce data movement across the
network, delegation is the result. In other words, rather than bringing data to
the app for processing locally, Power Apps will delegate data processing to the
data source.
The next stage is to limit
your use of formulas to those that can be delegated. The formula elements that
can be delegated are listed here. However, each data source is unique, and not
all of these elements are supported by all of them. In your specific formula,
look for delegation warnings.
ü Filtering, searching, and looking up information can all be delegated.
ü It's possible to delegate Sort and SortByColumns. The formula in Sort can only be the name of one column and cannot contain any additional operators or functions.
ü Sum, Average, Min, and Max are all tasks that can be delegated. At this moment, only a small number of data sources support this delegation; see the delegation list for further information.
ü CountRows, CountA, and Count are all counting functions that cannot be delegated.
ü StdevP and VarP are two other aggregate functions that cannot be delegated.
No comments:
Post a Comment
Thanks!