Thanks for coming back – this is the second part in a series of posts around combining my hobbies and my career. Here I will be tracking and monitoring my Destiny 2 gaming performance using the PowerPlatform! Part 1 can be found here.

Where to begin?

Firstly, I need somewhere to build. This is just for fun and personal development, so where can I do this work? Introducing the “PowerApps Community Plan“. I’d not heard of this until I stumbled on it from a random YouTube video – but it’s fantastic entry point into the world of the PowerPlatform. The more in depth details on what it is can be found here but the most simple criteria is you just need a “work or school account” (i.e. not a gmail!) and to have a license around Dynamics or PowerApps. I’ll hold my hands up here – I’ve VERY much on purpose stayed away from learning the Dynamics licenses, so my suggestion is just see if you can get a Community Plan on your account.

Data structure & storage

I come from a CRM background way back in CRM2011 (I avoided CRM4 and earlier – woohoo!) so I’m not going to stray too far from home at first and then slowly venture out of my comfort zone as time goes on.

I’ve started nice and simply by creating a brand new model-driven app that I’ll initially use to store all my data but thanks to the joys of the CDS, I intend on extending this same data set into canvas apps, PowerBI and beyond. Coming from a CRM background, I have a good knowledge of things like lookup fields, option sets and those other elements I’ve taken for granted for years so I’ll be using that to my advantage.

In my previous post, I’ve got a rough idea of what I need so I’ve built the basic data structure which will consist of two separate but linked parts. Part 1 is all around a person and will contain membership and character details and part 2 is all around the games themselves so will contain a record for each game, as well as a related “entry” for each person playing the game. If I’m making the effort to track myself and because storage isn’t an issue on a project so small, I’ll dynamic store other peoples statistics who are in my games – you never know where you’ll spot a pattern or when I’ll find a new in-game rival!

Sample model driven app build

With the model driven app experience being so strong, I already have my own custom app and have the initial data structure (I’m sure tweaks will be needed as I’m designing on the fly) within literally minutes!

Where next?

I would like as little human input as possible and thanks to Flow, I think I can achieve that. The total amount of input I wish to do manually is make an initial new “membership” record. From there, I would like the PowerPlatform to enrich the data and keep a constant track of my playing time.

Now I have my data structure in place, it’s time to jump across to Flow and build a custom connector. Building the custom connector could take some time, so that will be my next post coming soon!

Thanks for reading and please check back for Part III!


Leave a Reply

Your email address will not be published. Required fields are marked *