🪄🐈‍⬛ TnT #2 🧨

Ever wondered why you keep getting an error in Power Automate or Power Apps whenever you try to add a new record or update an old one? Ever wanted to see the data structure for a data source with type-specific data requirements?

Allow me to introduce my friends: the Parse JSON connector and curly braces {}.

The Parse JSON connector requires two (2) things:

1. A record, a list, or a table of records.
2. A schema of the data.

When I need to quickly check the output of a connector for a compose action, I run flows such as this. Running the flow for a SharePoint List Item provides an output of the entire record.

When the flow completes, I copy and paste the output into my favorite text editor. Then I reference back to the record in the text editor while creating the rest of my flow.

Bonus tips for Power Apps & SharePoint People-Picker Fields

The people-picker field type requires a record (for single selection) or table of records (for multi selection). Each record must contain:

• Claims
  • Internal users can typically use: “i:0#.f|membership|” & Lower(userEmailAddress)
• DisplayName
• Email

Set the default selection for a Combobox to the current user by entering the following in DefaultSelectedItems:

{
    Claims: "i:0#.f|membership|" & Lower(User().Email),
    DisplayName: User().FullName,
    Email: User().Email
}

Use a Parse JSON Connector with curly braces as the SchemaView of the Parse JSON connector after running the flow.Output of the Parse JSON connector, showing the entire record that was parsed.