One of my teams has a requirement to track the location of Stormwater equipment installations. IN this business the address where the equipment is installed rarely is related to any of the accounts involved on a deal (Engineering firm, Municipality, General Contractor etc..). i.e. sometimes these are installed in a segment of highway or other public/private area not necessarily associated with an Account in the traditional sense. Have other folks implemented additional custom address fields on the opportunity object? if so, any tips/ guidance on best practices are greatly appreciated.
@Vuk Stajic Thanks, I'm familiar with these. However, none of the limitations of Custom Address fields speak to the statement about not being supported during record cloning, which was my question Alina. I'm not sure if this was in response to that question or not?
It's also important to note that most of the limitations listed above are in comparison to standard address compound field functionalities. If you create your own separate custom fields to house additional address information you'll run up against most of the same, or just different, limitations. Additionally, virtually all of these limitations can be overcome without a ton of heavy lifting creating work arounds with RTFs or Apex Triggers. I don't really see any of these limitations outweighing the benefit of using them from an end-user standpoint. Custom Address is still a relatively new field so I'd expect many of these limitations to be addressed in coming releases as well, further increasing their value.
Everyone has their own opinion of course. :)
