Newbie here just getting into Dynamics.
An initial question that has come up is regarding choosing what entities to use for a specific business use case.
USE CASE
Residential service provider (security, audio/video, electrical, whatever). The pieces that are in play are:
individual - each person of the household that is a decision maker or is communicated with in some way
household - made up of multiple individuals that are communicated with, but this can change for example by divorce
location - the key entity that stores all communications/cases/invoices/data for the business relationship with that specific "address/building/etc", but this can change for example by a move or additional purchase
With that said it seems like with Dynamics fixed structure there's not an easy way to put these together as I think about them.
Therefore I would create a household as the account and then customers in the household added to that account. In the case of a split then the party leaving the current location would get a new account and then moved to that new account (CAN YOU MOVE CUSTOMERS BETWEEN ACCOUNTS)?
However, what is the "best" way to store a location such that all history stays with that location even up on the household(account) changing? Would you make each location an account and then make the household the parent account? (AGAIN ALSO CAN YOU MOVE A CHILD ACCOUNT TO A NEW PARENT ACCOUNT)?
