1,779
I have a custom entity - Property. On this, I need to record one or several addresses. What is the best way to accomplish this? Can I use the OOB Address entity or should I create a custom entity?
*This post is locked for comments
PM me with your email address, and I will send you sample source and instructions.
[quote user="Aric Levin"]
There are a few "Address" entities, such as Customer Address used for accounts and contacts, and Lead Address used for leads. The contain a few more address fields that what is just the Standard City, State, Zip, but you can replicate this functionality.
The thing is the there is logic between the Customer Address entity and the address fields that are stored in Contact or Account entity. There is basically a lookup control and address fields in the Account/Contact entity which point to the Customer Address entity.
If you don't need a separate entity, you can just add the fields to your primary entity. If you need multiple addresses, then I would create the related entity.
Regarding the Composite view of the address, there is no way to replicate this. In our implementation of this, however, we create a Custom Workflow (that works for various entities), where you enter the address fields, and it outputs the composite address, if that is something you are interested in doing.
Hope this helps.
[/quote]
Thank You. I think I will need to create a custom entity as the addresses recorded will not relate to either Accounts or Contacts and there will likely be more than one address I need to associate with my other custom entity.
Interested on the workflow you mentioned to build the composite view of the address. Can you provide any further information on this?
Yes, it simple like that, you can also create a common Address entity which you can use with other entities as well.
No, there is no way to have composite control, but you can replicate that kind of behaviour using custom development as suggested.
Thanks
There are a few "Address" entities, such as Customer Address used for accounts and contacts, and Lead Address used for leads. The contain a few more address fields that what is just the Standard City, State, Zip, but you can replicate this functionality.
The thing is the there is logic between the Customer Address entity and the address fields that are stored in Contact or Account entity. There is basically a lookup control and address fields in the Account/Contact entity which point to the Customer Address entity.
If you don't need a separate entity, you can just add the fields to your primary entity. If you need multiple addresses, then I would create the related entity.
Regarding the Composite view of the address, there is no way to replicate this. In our implementation of this, however, we create a Custom Workflow (that works for various entities), where you enter the address fields, and it outputs the composite address, if that is something you are interested in doing.
Hope this helps.
Hi,
Customer Address is only for account and contact, but you can create custom entity and store additional address there.
Thanks
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
#1
André Arnaud de Cal...
291,269
Super User 2024 Season 2
#2
Martin Dráb
230,198
Most Valuable Professional
#3
nmaenpaa
101,156
Share
Report
All responses (
Answers (