When to create a Custom Activity?

by Mar 14, 2024

When to create a Custom Activity?

I’m always very reluctant to create Custom Activities. They come with a lot of bagage.

Their stretch is excessively big, creating a lot of relations in all kinds of entities. Once you create a Custom Activity it’s kind of permanent: no walking back on your decision.

My rules before adding a Custom Activity: – is it a real action (start/end/status) – is it really core to your business, and it’s here to stay

What are your rules for adding Custom Activities?

Today I am torn how to add Marketing Interactions: Entity vs Activity?

Marketing Interactions are more like Events, like Email Opened, Email Clicked, Page Visited, Unsubscribed, Form Submitted, etc..

It could be nice to show time in the Timeline of a Contact, but it can also overflow the Timeline, pushing away more important activities.

Would you want to see these Interactions in the Timeline? Or is having a separate sub grid good enough?

#
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