
The next Dynamics 365 & Power Platform User Group meeting has been announced for the 24th November, and we can't wait to welcome you back to the Wesleyan for another packed session! As usual, we ask that you aim to arrive for around 6.30pm for networking and food ahead of a 7pm start from our first speaker. If you're driving in - you can park at the <a href="https://goo.gl/maps/kcTvM879cGgBWbaR6" target="_blank">B4 Car Park</a> just down the road - or if the train is more your thing we're a short walk from New Street or Snow Hill stations.

## Is this event for me?

It doesn't matter if you're a seasoned Dynamics 365 developer, or you're interested in your first foray into the world of the Power Platform - we aim to keep our meetings relatively beginner-friendly while looking at what is possible within this ecosystem.

---

## What does it cost?

Thanks to our wonderful sponsors, not a penny! We even provide tea, coffee and a buffet!

---

## What are the topics this month?

### Power Up Your Portal with Power Pages - Sheryl Netley

Announced in May 2022, Power Pages are the fifth product in the Microsoft Power Platform family. Power Pages are a new standalone product that empower low code makers and professional developers to create modern data-powered websites quickly and easily. Come along to find out how!

### The Art of the Possible: Spotify Clone using Power Pages and the wider Power Platform - Franco Musso

Fast forward a few steps from Sheryl’s excellent and empowering beginner-friendly introduction and see what customisation and extension possibilities lie ahead when you take the leap from no code to low code. Portals all look the same right? Wrong! Use liquid, FetchXML, JavaScript, the web API and a little Power Automate to break the mould and build a Spotify clone. Not ‘just’ the portal but the holistic solution. I’ll take you through challenges, workarounds and lessons learnt, showing how to style a portal while breaking through the usual form and list experience. Finally, I’ll leave you with my recommended learning path to get from point zero to portal hero; what to master and in what order.

---

## Where do I sign up?

We track registrations for the event on Meetup. For this specific event, you can <a href="https://www.meetup.com/d365ppug/events/287569402/" target="_blank">register here</a> - or join <a href="https://www.meetup.com/d365ppug/" target="_blank">our group</a> to hear about the various events across the UK!

## I want to speak at an upcoming event

Great! We'd love to hear from you. Head to <a href="https://sessionize.com/d365ppug-birmingham/" target="_blank">Sessionize</a> and fill in the short form to let us know.


Birmingham D365 & Power Platform User Group - November 2022 (The Power Pages Special)


Power Automate is an incredibly powerful tool, not only for businesses - but also for personal use! This is the first in a series of posts about fun Power Automate flows I create either for my own use, or as internal tools for my company.

The first flow I'm going to talk you through is my 'Track of the Day' generator using Spotify's API, a Custom Connector, and a Recurring Flow.

## Custom Connector

### Spotify Application

To start with - we need to gain access to the Spotify API. This is what we're going to use to select a random track. Head to the Spotify Developer Portal and create an Application. Give it a sensible name and description.

From the next page we'll need the `Client ID` and `Client Secret`. Make a note of these, as we'll need them shortly.

### Spotify API

Next on the agenda is to head to the Spotify API docs to look at how we'll build up our API URL. For this bot - we'll use the search endpoint with a few parameters. Add or remove as many as you like, but you should end up with a URL like the below.

`https://api.spotify.com/v1/search?type=track&q=T&offset=5&limit=1&market=GB`

I only want to search for tracks - and although eventually I'll provide a random `query` and `offset` - for now let's set them to `T` and `5` respectively. I'm also only interested in music I can listen to here in the UK - hence the addition of `market` to the end of the query.

Now we've got that endpoint URL - we can move on to…

### Creating the Custom Connector

To make the Spotify API available within Power Apps - you can use a Custom Connector. This basically functions as any other Trigger/Step would within a flow - but lets you define which API is being polled.

Within the [make.powerapps.com](https://make.powerapps.com/) UI - head to `Dataverse -> Custom Connectors` and create a new connector from scratch.

![Creating a custom connector within make.powerapps.com](/images/uploads/spotify-track/Create%20Custom%20Connector.jpg)

Now we need the host and the base URL. While we could be super specific at this point - I'm going to leave the options pretty open, as I might want to do other things with this connector in the future! Set the `host` to `api.spotify.com` and the `base URL` to `/v1` Hit next to move on to Security.

When asked which Authentication Type you'd like to use - pick `OAuth 2.0`. You can then select `Spotify` from the dropdown list of providers. Remember the `Client ID` and `Client Secret` we saved earlier? Now is the time to enter those into their corresponding fields. Once you've entered those - head to the top right of the page and hit `Create Connector`. Once it's saved - you'll be given a Redirect URL. Copy this and head back to Spotify.

Back on the Spotify Developer Dashboard, you can hit `Edit Settings` for your application, and paste the URL into a new `Redirect URI`. Scroll down and hit save.

### Connector Definition

Now you've successfully linked the Spotify API and your Custom Connector, it's time to do some fun stuff with it! Back in the Custom Connector - head to the `Definition` tab.

I found this page quite daunting when I first started looking into Custom Connectors, but the only bit we need to worry about is `Actions`. Let's create one now!

![General tab when creating a custom connector](/images/uploads/spotify-track/Custom%20Connector%20General%20Tab.jpg)

Once you've got the basic information above set up, head to `Request` and import one from a sample. We've already built the URL with query parameters above - so set the method to `GET` and paste the URL in. Hitting `Import` will generate the request. You can go into each query parameter in turn here and give it a description and summary if you plan on sharing this connector - but let's leave them be for now.

There's also a `Default Response` that we can edit which also allows an import from a sample! You can call the endpoint yourself using a tool like Postman - or use my result below…

```
    "tracks": {
        "href": "https://api.spotify.com/v1/search?query=T&type=track&market=GB&offset=5&limit=1",
        "items": [
            {
                "album": {
                    "album_type": "album",
                    "artists": [
                        {
                            "external_urls": {
                                "spotify": "https://open.spotify.com/artist/3luonLzvSOxdU8ytCaEIK8"
                            },
                            "href": "https://api.spotify.com/v1/artists/3luonLzvSOxdU8ytCaEIK8",
                            "id": "3luonLzvSOxdU8ytCaEIK8",
                            "name": "IC3PEAK",
                            "type": "artist",
                            "uri": "spotify:artist:3luonLzvSOxdU8ytCaEIK8"
                        }
                    ],
                    "external_urls": {
                        "spotify": "https://open.spotify.com/album/2Ji9U33Ljqdm4RdlBKXteF"
                    },
                    "href": "https://api.spotify.com/v1/albums/2Ji9U33Ljqdm4RdlBKXteF",
                    "id": "2Ji9U33Ljqdm4RdlBKXteF",
                    "images": [
                        {
                            "height": 640,
                            "url": "https://i.scdn.co/image/ab67616d0000b2739ec81d99271804ba71e6300e",
                            "width": 640
                        },
                        {
                            "height": 300,
                            "url": "https://i.scdn.co/image/ab67616d00001e029ec81d99271804ba71e6300e",
                            "width": 300
                        },
                        {
                            "height": 64,
                            "url": "https://i.scdn.co/image/ab67616d000048519ec81d99271804ba71e6300e",
                            "width": 64
                        }
                    ],
                    "name": "До Свидания",
                    "release_date": "2020-04-24",
                    "release_date_precision": "day",
                    "total_tracks": 12,
                    "type": "album",
                    "uri": "spotify:album:2Ji9U33Ljqdm4RdlBKXteF"
                },
                "artists": [
                    {
                        "external_urls": {
                            "spotify": "https://open.spotify.com/artist/3luonLzvSOxdU8ytCaEIK8"
                        },
                        "href": "https://api.spotify.com/v1/artists/3luonLzvSOxdU8ytCaEIK8",
                        "id": "3luonLzvSOxdU8ytCaEIK8",
                        "name": "IC3PEAK",
                        "type": "artist",
                        "uri": "spotify:artist:3luonLzvSOxdU8ytCaEIK8"
                    },
                    {
                        "external_urls": {
                            "spotify": "https://open.spotify.com/artist/4G1zP5i0r57g1c1CxrPhfM"
                        },
                        "href": "https://api.spotify.com/v1/artists/4G1zP5i0r57g1c1CxrPhfM",
                        "id": "4G1zP5i0r57g1c1CxrPhfM",
                        "name": "ZillaKami",
                        "type": "artist",
                        "uri": "spotify:artist:4G1zP5i0r57g1c1CxrPhfM"
                    }
                ],
                "disc_number": 1,
                "duration_ms": 184000,
                "explicit": false,
                "external_ids": {
                    "isrc": "QM6MZ2019111"
                },
                "external_urls": {
                    "spotify": "https://open.spotify.com/track/4A0YuzcYuEEP8A3oEZTddL"
                },
                "href": "https://api.spotify.com/v1/tracks/4A0YuzcYuEEP8A3oEZTddL",
                "id": "4A0YuzcYuEEP8A3oEZTddL",
                "is_local": false,
                "is_playable": true,
                "name": "TRRST",
                "popularity": 66,
                "preview_url": "https://p.scdn.co/mp3-preview/b7566fbd093279b80b7dd4b54a9bc98e6cf5326c?cid=936141d3c27142c2bb4a82af14c5a9d3",
                "track_number": 9,
                "type": "track",
                "uri": "spotify:track:4A0YuzcYuEEP8A3oEZTddL"
            }
        ],
        "limit": 1,
        "next": "https://api.spotify.com/v1/search?query=T&type=track&market=GB&offset=6&limit=1",
        "offset": 5,
        "previous": "https://api.spotify.com/v1/search?query=T&type=track&market=GB&offset=4&limit=1",
        "total": 10180
    }
}
```

Again, this will generate a load of fields under the 'Response' which you could give titles to represent them better. Once this is done, hit `Update Connector` and head to the `Test` tab - and create a new connection. This will request access to your Spotify account - but we gave the application no scope, so it won't be able to read any of your personal data!

When your connection is created, navigate back to the Custom Connector's test tab - and fill out the information against the 'SpotifySearch' action. If the test succeeds - congratulations! You've just created a Custom Connector calling an external API.

Next up, let's build a flow to use that Connector!

## The Flow

Now we've got the Custom Connector up and running - let's head back to [make.powerapps.com](https://make.powerapps.com/) and create a new Automated Flow from scratch!

For my trigger, I have a `Recurrence` set up as below. It will trigger every week day at 8:30am for my time - but feel free to tweak to suit your scenario!

![Screenshot from within Power Automate](/images/uploads/spotify-track/Flow%20Recurrence.jpg)

I then initialize two variables - one is just a string of every letter in the alphabet, and another which generates a random number between 1 and the length of your first variable - and then subtract 1 so we can correctly get the array index of the letter (see my syntax below).

`sub(rand(1,length(variables('Alphabet'))),1)`

You can then use a Substring operation along with the Alphabet and Index variables like the below screenshot to fetch a random letter!

![Example of a substring PowerFX within Power Automate](/images/uploads/spotify-track/Flow%20Substring.jpg)

Now we've got our random letter, you can either generate a random number, or (as I'll do here) use a static number for your 'offset'.

It's time to bring in our Custom Connector! Add a new step, head to the Custom tab and bring in your `Search Spotify` action. Fill out the fields as below - or mix it up for your flow!

![Using a custom connector within Power Automate](/images/uploads/spotify-track/Flow%20Spotify%20Connector%20Filled.jpg)

For my flow, I'm only really interested in the Artist, Song Title, and the URL to the song - but the Spotify action returned a whole bunch of stuff! I've created three new string variables to pull that information using expressions. You can navigate around the JSON response from the server this way - and it's quite handy to pick specific items as opposed to having masses of data available.

### Artist Name

`outputs('Search_Spotify')?['body']?['tracks']?['items'][0]?['artists'][0]?['name']`

### Song Name

`outputs('Search_Spotify')?['body']?['tracks']?['items'][0]?['name']`

### Spotify Link

`outputs('Search_Spotify')?['body']?['tracks']?['items'][0]?['external_urls']?['spotify']`

All that is left to do then is share your track of the day! In this example, I've opted for a Teams message directly to me - but you could post it into a channel that is shared with other members of your team, or even style it as an Adaptive Card (as I did with our company one)!

![Plain Text generated by this flow](/images/uploads/spotify-track/Flow%20Teams%20Message.jpg")
![Result of flow styled as an adaptive card](/images/uploads/spotify-track/Flow%20Adaptive%20Card.jpg)


Spotify Track of the Day in Power Automate


Are you more likely to open an email addressed to you by name, or to a `valued customer`? Personalization in Marketing Communications is an absolute must these days - whether it be through your email correspondences or landing pages.

In Dynamics we have the `Personalization` menu available to us - which allows you to look at embedding either Dynamic (differs by who you're talking to) or Static (stays the same regardless) content. The most common usage I've found is to select attributes stored directly on the `contact` entity, such as their first name - or drilling into the Account from the contact to get the company name.

![The 'Content Assist' window within Dynamics 365 Marketing](/images/uploads/marketing-personalization/marketing-content-assist.jpg)

But what happens when your data doesn't include the fields you've used in your personalization? In Realtime Marketing we have an option for defining a default value for each 'token' - but that hasn't made it's way to Outbound Marketing yet. Don't fret though! There is something we can do to resolve this - and it has something to do with those curly brackets around our data!

Handlebars is a popular templating language - and is used in Dynamics Marketing when embedding data from the Dataverse. The above example looked directly at the `contact` entity, and then at the `fullname` attribute - but Handlebars allows for much more than basic data selection, such as [if statements](https://handlebarsjs.com/guide/builtin-helpers.html#if) and [each loops](https://handlebarsjs.com/guide/builtin-helpers.html#each).

The most common problem I've run into is addressing the reader, even if I don't know their first name. To avoid setting up a condition on your Customer Journey - you can utilise the below handlebars snippet:

```
Hello {{#if (ne contact.firstname '')}}{{contact.firstname}}{{else}}customer{{/if}}
```

Most handlebars 'helpers' start off with the hash symbol, in this case #if. We then have a query in normal brackets that will return true or false. In this example we're looking to see if the contact's first name is not equal (`ne`) to an empty string. For anyone that has a first name, this will return true, and we can display the first name as normal - otherwise we'd like to display something else (like 'customer').


Blog

Birmingham D365 & Power Platform User Group - November 2022 (The Power Pages Special)

Spotify Track of the Day in Power Automate

Making your Marketing Emails More Personal