In my previous post, I wrote about updating the status of the child and the children of these child records. Now that we already are able to get hold of the child records, what I want to do this time is to select details from these records and add them into the body of an …
State Update of Child Records via Custom Activity Workflow and Flow
Suppose we have an entity relationship in which Entity A is the parent of Entity A.1, and Entity A.1 in turn, is the parent of Entity A.1.1. Further, the status transition is as described in the picture. What we want to achieve is to update the status of all related records in Entity A.1 and …
Continue reading "State Update of Child Records via Custom Activity Workflow and Flow"
A Virtual (Entity) Exercise
I have never had to deliberately learn what virtual entities are and what they are for. Sure, I might have come across it in blogs I have read, but that's where the story ends. That is, until last week. One of the elements in the design being looked at for a project with a client …
About Relationships :)
Relationships establish a connection between records. In Dynamics 365, entities can modeled to have either a one-to-many or many-to-many relationship with another entity. A one-to-many relationship (1:N) is a hierarchical, in which a record from one entity can have one and only one parent record from another entity. The parent record, on the other hand, …
Business Units and Teams
Business Units are handy if there is a need to impose data access restrictions. There are cases however that a user belonging to a business unit may still need to have access to records belonging to the other business units. Case: User A belong to Business Unit A User B belongs to Business Unit B …
Striving to Make Things Count 