I have a need to associate addresses with some custom entities and provide similar address functionality to what is available on Vendors, Customers, Operating Units, etc...
However, I have noticed that these forms all use a custom form pattern for the address tab. When I follow the same approach, the functionality is great and I'm able to create multiple addresses for my entity. However, I get a best practice warning stating that I should avoid custom form patterns:
BPWarningFormDesignOrControlsWithCustomPattern: BP Rule: [BPWarningFormDesignOrControlsWithCustomPattern]:Path: [dynamics://Form/PCGOMOperatingUnit/FormDesign/FormDesign/FormTabControl/Tab/FormTabPageControl/AddressTab]:BPWarningFormDesignOrControlsWithCustomPattern: 'AddressTab' is using the 'Custom' pattern. Please apply one of the other available patterns.
Are there any good alternatives for creating an address tab and avoiding this best practice deviation? Thanks in advance for any suggestions.