Power Platform and Dynamics 365
A few years ago, I wrote about ten different types of Dynamics 365 projects. One of these types of projects I referred to as a “drive-by”. A drive-by implementation is where someone, often a supplier, is interested in getting paid, and getting out as quickly as they can, leaving an implementation project to slowly fail.
You might end up being the victim of a ‘drive-by’ through : Continue reading “Avoiding a Power Platform “Drive-By” using the Centre of Excellence Starter Kit”
Just before I started my working career, I completed a social sciences degree in Communication Studies. For the most part, this was a non-technical IT degree. It was one which made me think deeply about the day to day encounters I have with other people, written, verbal and more. With the job market not being awash with social science jobs at the time, and having hacked around a lot with BBC Basic on an old BBC Micro and Acorn Archimedes in my formative years, I felt a pining for programming again, so I forged a career in the IT industry. I’ve been here ever since. Continue reading “Five ways to become a Software Engineering Multiplier”
Tech intensity refers to an organisation’s ability to turn tools and technologies into their own problem-solving digital solutions.
If you are looking at using Canvas Power Apps to solve business problems, you might wonder where you should store your data.
Here’s another two minute video I created to show what you should consider.
Do you know the difference between perpetual and subscription licensing, or know your multiplexing from your software assurance?
Here’s a quick three minute explainer for Power Platform licensing concepts you should understand if you plan to buy Power Platform or Dynamics 365 licences any time soon.
If you’d like a similar explainer for another Power Platform topic, please let me know.
Are you starting a new Power Platform or Dynamics 365 Project and not sure where to start or how to frame the requirements?
Here’s a short explainer video I’ve created to get you thinking about the reasons for building a prototype and what you can hope to achieve through building one and demonstrating it to your prospective users or business stakeholders.
I normally do my weekly grocery shopping online, however since the Coronavirus lockdown and because of the shortage of home delivery slots, I have the first world problem of visiting the supermarket again in person! After returning from a shopping trip this week, I saw a meme on twitter which reminded me of the dilemma most supermarket shoppers face after unpacking their shopping into their car – namely looking at the empty shopping trolley and wondering where to return it to. To quote the tweet :
Continue reading “Returning the Shopping Cart – Being a Good Power Platform Citizen Developer”
I really enjoy the early phases of new greenfield Microsoft Business Applications projects. It might be delivering a fixed scope project with expected outputs already defined. It might be formulating and documenting new requirements for a truly agile project. Fundamentally however, it’s about getting into the minds of business users, perhaps building some SFDs and mapping the technology to participants, perhaps unknown, wants and needs. Continue reading “Five Tips for Running Remote Discovery Workshops during a Pandemic”
There are a myriad of new features being released to Dynamics 365 and the Power Platform right now. It’s tempting to try out new features and, perhaps push a new feature through to production if you or your customer is willing or agile enough. For some larger organisations however, there’s more of an importance placed on standards and governance than ensuring the continued agility of getting new features and new applications quickly to production.
But how do, or how should Enterprise Architecture standards apply to those of us who have invested our time in these newfangled Power Platform based solutions. How can we ensure an organisations approach is both agile and structured?
A lot has been said and written about ‘Portals’ since Microsoft bought ADX Studio in 2015. If you are unaware of the background, ADX Studio at the time was the de-facto market leader and default solution for building portals to front and expose data from Dynamics CRM.
With the ADX Studio product being built in a configurable way, it seemed like a good acquisition from Microsoft. This was a departure from earlier acquisitions of technically different products which had to be integrated to Dynamics – see Parature (cough) or Marketing Pilot (splutter), which have since died a slow death. ADX Studio was a product that, on the face of it, could more easily integrate and slot in to the new approach.
Since 2015, Microsoft has been on a journey to integrate and extend this old ADX codebase onto what has since become Dynamics 365 and, more recently, the Power Platform. ADX Studio in its old form – a .NET website and configurable code framework – is now effectively dead* – the Microsoft shift to the cloud is nearing completion, with new features being added regularly. Continue reading “PowerApps and Dynamics Portals Design Decisions”
A few months ago I met an old colleague – let’s call him Ben, and we got talking. He is an experienced Microsoft developer now working on a greenfield Dynamics 365 project. He’d picked Dynamics up quickly after a few months training and upskilling himself, and had a good grasp of the platforms functionality and extensibility techniques. Our conversation went something like this :
Him : I’m working on a potential 200 seat project for <financial organisation> for a Sales Process. I’m going to automatically create a lead when my custom entity changes status and allocate it to the correct sales manager.
Me : Are the sales guys using Leads at the minute or how are they tracking leads outside of D365 – spreadsheets / access / onenote?
Him : Not sure, but that’s what’s going to happen – the Business Analysts have already modelled it in our new process flow diagrams. Once the lead is qualified, we need a trigger to create a case against the related account so another team can track the lead.
Me : What is the purpose of the case? Are you sure you need to use the case entity here?
Him : It’s mainly just for tracking purposes, but the new process says we might need the ability to merge cases sometime in the future. I’ve nailed the security model for cases and leads based on our to-be business units. Dynamics is great for that.
Me : Ok,it’s good you are thinking about security. Have you considered the licences each of these users might need alongside the security rules?
Him : No, that’s not my department, my manager deals with that, I just have to design and build the solution before year end. Licences are in next year’s budget. The project needs to save the company £200k per year by year two.
Me : Hmm. Let’s discuss this in more detail.
The conversation with Ben got me thinking about my approach to initiating projects and how my approach to development and design has evolved over the years across a variety of software projects. Methodologies included :
