Connections in Dynamics 365. Should we still use them?

by Jul 10, 2023

Connections in Dynamics 365. Should we still use them?

Connections are very flexible and could be an option for some use cases. But most of the time I don’t recommend them.

Why? The User eXperience is so horrible. Users don’t get how it should work.

The problem: It’s very flexible under the covers, but the UI is not hiding this flexibility. It’s just dumping the low-level way of storing the data into the face of the user and let them sort it out.

For most use cases, you want to trim the UI for that specific use case. It could be only one type of role is allowed. It could be that you are only allowed to connect to Contact that fits a certain filter.

We need an additional wizard or business rule layer on-top of Connections to make it acceptable for users to work with it.

Also showing Connections confuses users. When I click on a connection in a sub grid, I expect to go to the entity/table that is connected, like a Contact or Account. Not the Connection itself…

Microsoft please decide: make it obsolete or improve the User eXperience!

#
Remy van Duijkeren

Remy van Duijkeren

Power Platform Advisor

Microsoft Power Platform Advisor with over 25 years of experience in IT with a focus on (marketing) automation and integration.

Helping organizations with scaling their business by automating processes on the Power Platform (Dynamics 365).

Expert in Power Platform, Dynamics 365 (Marketing & Sales) and Azure Integration Services. Giving advice and strategy consultancy.

Services:
– Strategy and tactics advise
– Automating and integrating

Subscribe to
The Daily Friction

A daily newsletter on automation and eliminating friction

Related Content

Backlog: The Black Hole of ideas

Backlog: The Black Hole of ideas Is your backlog turning into an ever-expanding universe of forgotten dreams? We all know that mix—a jumble of big ideas and tiny tasks waiting for their day in the sun. Some items linger for years. Why do backlogs grow? Because we...

read more

The Trade-off Between Budgets and Quality ⚖️

The Trade-off Between Budgets and Quality ⚖️ In my previous post, I talked about shifting from Estimates to Budgets for feature development 💡. Let's dive deeper. Using a Budget instead of an Estimate introduces a trade-off: Scope and Quality adjust to fit the time...

read more

Budgets instead of Estimates

Budgets instead of Estimates Estimating a feature is difficult and is often a guess (or even a lie). An Estimate is for a fixed scope. So, you need to think deeply how to implement the feature, before giving an Estimate. The business can then use the Estimate to...

read more