Have you ever had that requirement where you know you can solve most of it with a workflow but the information you are after is one relationship too far away? For example:
I have a custom entity called Event Registration that is related to Contact but the discount information is placed on Account.
This article will explain how you can use an action as a placeholder for that information that is out of reach, and use it in your workflow either as a condition or to populate a field.
Refining your Resource search in URS
In my previous post I wrote about how to enable a custom entity for scheduling with Universal Resource Scheduling, a part of Dynamics 365 Customer Engagement. In this post I will take it one step further, and help to refine our resource search with the help of a workflow.
This is part of a series of articles about Universal Resource Scheduling (URS) and examples on how to customize and use it for custom entities.Continue reading “Refining your Resource search in URS”
Get started with Universal Resource Scheduling
Universal Resource Scheduling is the scheduling engine in Microsoft Dynamics 365 Customer Engagement that allows you to enable scheduling for any entity, even custom entities. It’s used to find the best resource based on a set of different variables for example availability, skill set and location.
I know what you are thinking… Even custom entities? But how? What should I think about?
Well let me show you how I’ve done it!
This is the first of a series of articles about Universal Resource Scheduling (URS) and examples on how to customize and use it for custom entitiesContinue reading “Get started with Universal Resource Scheduling”
