According to Dynamics Learning Portal´s official video by Derick Bormann 'https://mbspartner.microsoft.com/D365/CourseModules/1441', it quotes: "you don't necessarily have to have a relationship between the entities. It is nice and there's an argument to be made for having a relationship, because if you have a relationship between the entities, now you can do things like auto-closing a previous entity".
According to MS Documentation: "You can design business process flows that tie together the records for up to five different entities into a single process so that people using Dynamics 365 can focus on the flow of their process rather than on which entity they are working in. They can more easily navigate between related entity records."
They don't mention that they "need" to be related, only if that they are, it is easier to navigate between them.
A voting comment increases the vote count for the chosen answer by one.
Upvoting a comment with a selected answer will also increase the vote count towards that answer by one.
So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.
javier
5 years, 2 months agodaisy
5 years, 4 months agoj_ulate
5 years, 8 months agoelina
5 years, 9 months ago