A collection of snippets and samples related to the Power Platform.
Little snippets, functions, and code that I want to remember later.
In this article
EN-US $2,000.00
Text( currencyfield, "[$-en-US]$ #,###.00" )
The key to this one is to pass in a legit date/datetime value. If the source field provides the field as a Date, you’re good to go. Use the DateValue() or DateTimeValue() function as needed to adjust the source from Text to Date
Text(date or datetime field, "[$-en-US] yyyy-mm-dd hh:mm:ss.fff AM/PM" )
(adjust the yyyy-mm-dd... part as appropriate)
More comprehensive details on docs.microsoft.com
"I would like ""this"" to be in quotes." // Reads: I would like "this" to be in quotes.
When I have an app where I want to reference specific fields, but I haven’t attached to a data source, I like to use a Collection as a placeholder. This allows me to use similar data to get things looking right.
The following example is from an app where I later populated a URL list based on a search query. Simple 2-column blank table:
ClearCollect(flowSiteURL,{url:"",name:""});
The format with sample data and additional rows can look like this:
ClearCollect(flowSiteURL,{url:"https://make.powerapps.com",name:"Power Platform Maker Portal"},{url:"https://connectingthedata.com",name:"Connecting the Data website"});
At the end of a Power Automate Flow, you can return data to the app. When calling the Flow, call it as the table value for a Collection.
ClearCollect(varFlowResponse,FlowName.Run())
This won’t behave correctly if you modify the Response format in the Flow after it’s been added to the Power App. The collection will become a single value of True even though the full payload is there. The fix for this is to remove all references to the Flow, save/close the Power App, then open and re-add the Flow.
In the following, I’m creating a local Collection, which includes a few columns from a related table.
I’ve already pulled the related table into a local collection LocalFoods so the LookUps don’t get chatty with network calls to the data source.
ClearCollect(LocalInventory,
AddColumns(Filter(Inventory,Gone=false),
"FoodName", LookUp(LocalFoods,UPC = ParentUPC).Title,
"FoodSize", LookUp(LocalFoods,UPC = ParentUPC).Size,
"FoodSearchTags", LookUp(LocalFoods,UPC = ParentUPC).SearchTags,
"FoodUnits", LookUp(LocalFoods,UPC = ParentUPC).UnitsInPackage
)
);
Things to remember: for the LookUp, the first parameter is the “parent” table, the second parameter starts with he column I’m comparing in the second table…this gets the record. Then I returmn the specific .Field as the result for the column.
LookUp(LocalFoods,UPC = ParentUPC).Title
^ ^ ^ ^
| | \ `----.
[Parent Table] [Parent Field] [Match value] [Returned Field]
In the future, if you need to update the formulas, simply change the fncMyFunction.OnChange Action property. All of the rest of the references can stay as they are.
Credit: Code re-usability in Power Apps
The Power Platform Creator Kit includes a theme designer (which is verrrrrry similar to this Fluent UI Theme Designer).
To use these in the app, I set a variable with multiple properties:
Set(AppTheme,
{ palette:
{
themePrimary: "#0078d4",
themeLighterAlt: "#eff6fc",
themeLighter: "#deecf9",
themeLight: "#c7e0f4",
themeTertiary: "#71afe5",
themeSecondary: "#2b88d8",
themeDarkAlt: "#106ebe",
themeDark: "#005a9e",
themeDarker: "#004578",
neutralLighterAlt: "#faf9f8",
neutralLighter: "#f3f2f1",
neutralLight: "#edebe9",
neutralQuaternaryAlt: "#e1dfdd",
neutralQuaternary: "#d0d0d0",
neutralTertiaryAlt: "#c8c6c4",
neutralTertiary: "#a19f9d",
neutralSecondary: "#605e5c",
neutralPrimaryAlt: "#3b3a39",
neutralPrimary: "#323130",
neutralDark: "#201f1e",
black: "#000000",
white: "#ffffff"
}
}
)
Then instead of specifying specific colors in my app, I’ll reference AppTheme.pallete.themePrimary or AppTheme.pallete.neutralPrimary instead of the RBGA value (or color name). Also, this works with the Template apps.
Then, later, if I want to modify the colors in my app later, I can update this one variable and it’s immediately reflected throughout the app.
Those who have followed this resource probably saw a variant on this with far fewer colors. While this is definitely a lot more to choose from, it’s not really so complex. I explored some more of the Fluent UI theme designer web app “semantic slots” detail and came up with my most important subset of colors:
I use the same approach for fonts, though admittedly I’m still trying to find the sweet spot of how much to define/automate this way. Note, I haven’t updated the AppTheme variable to include fonts, but the template apps aren’t expecting it either.
Set(MyFont,
{
FaceHeader: Font.'Lato Black',
FaceBody: Font.'Lato Light',
SizeH1: 28,
SizeH2: 24,
SizeLarge: 16,
SizeStandard: 14,
SizeTiny: 12
}
)
This approach is also useful for other general properties that need to be set for various controls. I borrowed the target list from the Center of Excellence theme editor.
Set(myProperties,
{
TextBoxHeight: 80,
RadiusValue: 5,
PaddingValue: 8,
BorderThicknessValue: 0,
FocusedBorderThicknessValue: 0
}
)
To save time on setting these properties, I try to use copy/paste of a similar control that I’ve already treated (in favor of adding a new one from the control library). That said, if I have multiple components to update at once, I’ll multi-select these from the navigation view, then use the formula bar to choose he property (such as Font) then set all of the selected components to MyFont.FaceBody.
The following example assumes you are tracking volunteers and the organizations with which they volunteer. Any given volunteer (Contact) can volunteer with multiple organizations (Accounts) and the Dataverse N:N relationship has been created between the Account and Contact to represent this.
The following sample relates a volunteer contact (selected in the gal_Contacts gallery) with an Account (selected in the gal_Account gallery).
Relate(gal_Account.Volunteers,gal_Contacts.Selected)
The format of the function is to identify a record in a table then the relationship name via dot notation (.Volunteers) as the first parameter, then the related record as the second parameter.
JavaScript is supported as well, so there are some functions included below as well.
There’s probably a more elegant way to use a single JavaScript function, but hey, it works :)
The following must be uploaded as a JavaScript web resource. It hard codes the page name for simple build, but I’m sure there’s something more elegant that someone can come up with to pass it in as a parameter to the function.
function openFullPageFromGrid(selectedItems)
{
let selectedItem = selectedItems[0];
if (selectedItem) {
let pageInput = {
pageType: "custom",
name: "ctd_custompagelogicalname_35171",
entityName: selectedItem.TypeName,
recordId: selectedItem.Id,
};
let navigationOptions = {
target: 1
};
Xrm.Navigation.navigateTo(pageInput, navigationOptions)
.then(
function () {
// Handle success
}
).catch(
function (error) {
// Handle error
}
);
}
}
function openFullPageFromItem(selectedItem)
{
// Inline Page
var pageInput = {
pageType: "custom",
name: "ctd_custompagelogicalname_35171",
entityName: "ctd_table",
recordId: selectedItem,
};
var navigationOptions = {
target: 1
};
Xrm.Navigation.navigateTo(pageInput, navigationOptions)
.then(
function () {
// Called when page opens
}
).catch(
function (error) {
// Handle error
}
);
}
Calling from the Main grid:
openFullPageFromGridNote, I’m also including a rule to only show the button when a single record is selected.
CountRows(Self.Selected.AllItems) = 1
Calling from the Record form:
openFullPageFromItemThe parameter that gets passed to the page has a slightly different format, it may include curly braces {}, so when consuming the parameter, make sure to strip out the braces in most cases. Example formula is below.
Set(RecordItem,
If(IsBlank(Param("recordId")),
First('Table'),
LookUp('Table', 'RecordId' = GUID(Substitute(Substitute(Param("recordId"),"{",""),"}",""))))
)
I can never seem to remember the Patch() command when setting an Opportunity Potential Customer in Dynamics 365 Sales. The bare bones are:
Patch(Opportunities,Defaults(Opportunities),{
Topic: "Test",
_customerid_value: varMyCustomerRecord
})
Where varMyCustomerRecord is a variable set to the Record for an Account or Contact. Defaults(Opportunities) is used to create a new Opportunity, but this could reference an existing Opportunity Record.
Check to make sure the proper name@domain.extension format has been followed. This is more precise than other approaches that rely on the “IsMatch(myFancyText,Email)” which can provide false positives.
IsMatch(myFancyText,"^([a-zA-Z0-9_.-])+@(([a-zA-Z0-9-])+.)+([a-zA-Z0-9]{2,4})+$")
The example below is from a button, if the input_email control has an email address, then collect that email address, otherwise send up a notification.
If(
IsMatch(input_email_1.Text,"^([a-zA-Z0-9_.-])+@(([a-zA-Z0-9-])+.)+([a-zA-Z0-9]{2,4})+$"),
Collect(col_invitees,{channel:"email",value:input_email_1.Text});Reset(input_email_1),
Notify("Please use a valid email address",NotificationType.Error)
)
I had a requirement to take a parameter of a phone number, but the phone number may have unexpected formatting (some may have parenthesis, dashes, spaces…nothing consistent).
I used the MatchAll() function to grab all of the digits from the string (relying on a regular expression for matching), then wrapped with the Concat() function to squish them all of the “FullMatch”es back together.
Concat(MatchAll(myFancyEmail.Text,"\d"),FullMatch)
In this case, the value of “abc(800) 555-1234” returns “8005551234”, which I could use consistently through the app.
More on matching functions can be found here: https://learn.microsoft.com/en-us/power-platform/power-fx/reference/function-ismatch and I like
I have several apps where I launch unscheduled (ad-hoc) Teams voice calls.
To dial out to a traditional phone number, I use the following format to prepend the phone number.
Launch("https://teams.microsoft.com/l/call/0/0?users=4:"&varFancyPhoneNumber)
Note, the important thing is the 4: before the phone number.
More examples on Microsoft Learn
Upon learning about the upcoming feature of Named formulas in a Power App, there are some opportunities to standardize some common operations. One of those is passing a record into a Canvas App.
varMyRecord=If(
IsBlank(Param("RecordId")),
LookUp('Contacts','Contact'=GUID("b57974f4-b403-ed21-82e4-000d3a997ecc")),
LookUp('Contacts','Contact'=GUID(Param("RecordId")))
);
The upshot of this approach is that this can be used with a Debug flag in the app, to add in a check for the If statement.
For simplicity, I am assuming a valid ID is passed if Param() is not blank…but error handling should be considered in how your app should behave if a bad GUID was passed.
In a label field, sometimes I like using a flexible height, but other times I just want to cut off the text in a way that shows there’s “more”.
If(Len(ThisItem.Name)>25,Left(ThisItem.Name,25)&"...",ThisItem.Name)
The example above is used for a Label control inside of a Gallery.
Set the ComboBox.DefaultSelectedItems property to a Table() value. Something like this:
Power Fx
Table(
LookUp(Users,User=GUID("b83c01bc-7cc2-ed11-83af-000d3a1a02cb")),
LookUp(Users,User=GUID("511d59f1-5de8-ed11-a6c6-000d3a1a02cb"))
)
This will ensure that the full record is selected, which becomes important when referencing field values in other formulas.
Canvas Power Apps formula reference
Regular Expression Builder - this is the online tool I use to hack out the regex expressions I can’t easily find in a web search.