Best way to setup address book in Ax7

(0) Share

Report

Posted on by Mav

Can anyone suggest best way to setup Addresses in AX7, requirement are In AX2012 we could simply use service calling into Address table group and logic running for validation event at forms. Looks like it has changed in AX7 as I cannot see addressbookimport table and related tables.

My requirement along with my best way to solve it is shared below, I am keen to know if there is any other better approach.

1st

The format should be

Street 1

Street 2

Street 3

City

State -Zip

Country

2nd

No duplicates are allowed.

Now I went through the application and as per me the best way would be to use the address format with out of box parameters like

Street code

Street Number

Street name

City

State - Zip

Country and

However I am not sure of data types in Street code and street number, if it accepts same as street name then I can solve my issue without extending anything .

For my 2nd requirement I can see options like Use duplicate checks and Check for unique DUNS under GAB parameters, looks like enabling these would ensure that no duplication is allowed.

*This post is locked for comments

I have the same question (0)

All responses (6)

Answers (1)

Mav on at

Like (0)

Report

Can anyone please respond

Was this reply helpful? Yes No
André Arnaud de Cal... 301,146 Super User 2025 Season 2 on at

Like (1)

Report

Hi Mav,

What is the exact requirement and what had you done in AX2012 to achieve this? Functionally there is no real difference between addresses in AX2012 and Dynamics 365 (formerly known as AX7). The street name is a multi-line field, so can contain already multiple lines. What makes you think you need the street code and street number?

There are several ways to prevent duplicates. I wrote a book about it. The DUNS number is one, but not all companies did apply for this number. You can search for duplicates on address and contact information, but a slightly different entry will not be recognized. Like "Elmar Street" or "Elmar st." This will not be recognized.

Was this reply helpful? Yes No
Mav on at

Like (0)

Report

Thanks for responding

Requirement is to have address book extended in a way that prevents users from entering duplicate data.

In Ax 2012 I asked my partner to develop a solution , which if i remember correctly use to check on all related address tables when user used to click on submit button, the validation method use to inquire into associated tables and match it against what user has entered.

I am trying to do same here, i did see logisticspostaladdress table with multiple validation methods on that table.

Looks like that customizing this would do it.

I am not going the DUNS route, as i understand that DUNS is only applicable for vendors or businesses, i need to have individual customer data address , who will not have DUNS.

My current system has street 1 & street 2 , i was thinking if I can have same in d365 then data migration and user training will be faster.

Was this reply helpful? Yes No
Suggested answer

André Arnaud de Cal... 301,146 Super User 2025 Season 2 on at

Like (1)

Report

Hi Mav,

Street number is limited to 20 characters. So this cannot be a replacement for Street 2 or 3.

To be able to do create fields like the customization in AX2012, you should possibly also customize the base enum LogisticsAddressElement. This enum is not extensible, meaning that you will overlayer standard models from Microsoft. If you do so, upgrading or installing fixes would be a bit more cumbersome.

You can try to see if using an extension model could be used where you don't change the enumeration, but will add Street 2 and 3 where it also will show the default Street field. The Street 2 and 3 can be added with an extension. A developer should check the coding if overlayering can be prevented for this.

Was this reply helpful? Yes No
Mav on at

Like (0)

Report

Thanks , I am developing this solution which would ensure no duplicates in addresses in d365.

My understanding is , that in order to achieve no duplicates in the address book, I have to work with already existing validation methods defined under logisticspostaladdresstable and if required customize them to meet my requirement, final product will be when ever user clicks on submit on any form , click event will call this table validation and if the address already exisits it will pop out dialog box error and if not it will commit the changes to form.

I have to use this for each and every form, which serves as entry point to enter the address in d365. Also as mentioned cant go the DUNS route as we have residential customers who will not have Dun. Please share your views.

Was this reply helpful? Yes No
Verified answer

André Arnaud de Cal... 301,146 Super User 2025 Season 2 on at

Like (0)

Report

Hi Mav,

You are correct in extending validation options on table level. You have to test if it also works on the address creation form correctly. We had some issues with this form with out Data Validation Framework add-on, but I don't know the details how it is solved. The problem was that when a user clicked OK to save the address and close the form, a validation error occurred and the form closed too. Then a user had to re-enter the full address details. We solved it, but I don't know exactly how.

Was this reply helpful? Yes No