Personalized Community is here!
Quickly customize your community to find the content you seek.
Have questions on moving to the cloud? Visit the Dynamics 365 Migration Community today! Microsoft’s extensive network of Dynamics AX and Dynamics CRM experts can help.
2022 Release Wave 2Check out the latest updates and new features of Dynamics 365 released from October 2022 through March 2023
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Community | FastTrack Program | Finance and Operations TechTalks | Customer Engagement TechTalks | Upcoming TechTalks | All TechTalks
At my organisation, our products are installed in homes, so the home is most important record we want to track, potentially as an account. The home owner, or person renting the home, would then be connected as the primary contact,
Does anyone have any advice for best practice and how to achieve this?
For example, auto-generating accounts from contacts and setting them as the primary contact.
Account Name: 123 Tree Avenue, Forest Hill, Cityville
Contact: John Smith
I would highly recommend not to use Account as House and create a custom "House" entity.
Once the entity is created you can add relationships between "House" and "Contact" and track that relationship between records.
Hi Andrew, can you explain why you wouldn't recommend using Account?
Not all our 'accounts' are houses, as we sell to retailers. But we do still need to capture the house/consumer information for a different purpose.
Is it along the lines of this article which suggests creating a site and copying the address?
CloudThing | The Problems With Addresses In Microsoft Dynamics 365 - CloudThing
My point is that it's better not to reuse something that wasn't created for the purpose you want it to use.
It's clear that you can break the wall using the microscope. But it's better to find the sledgehammer for this purpose.
If you want to use Account as "House" entity, I prefer to add a custom field inside "Account" Entity , for example let say its: "Account Type" as an OptionSet.
Then add in the options those:
Then use the entity with same name "Account", and just change the type.
This is my suggestion if you want to work with the OOB Entity Account.
Business Applications communities