Microsoft Dynamics AX (Archived)

Trouble in fetching new location role logisticslocationRoletype enum in coding

(0) Share

Report

Posted on by Lakshmi Karambakkam

1,307

Hi,

LogisticsLocationRole table is used for creating addresses for customers.

I added a new location role to LogisticsLocationRole for our customers and I have a problem in using it for coding.

I tried to see the value from AOT\Data Dictionary\Tables\LogisticslocationRole table.

here, the type of this new location role is "user Defined". This is a default value and it cannot be changed. But I have to change it to VASAltDLV to fetch VASAltDlv record. The record I am creating in the form is not taking the label from the VASAltDlv ENUM instead it is by default showing as "User Defined" only.

In logisticsLocationRoletype, the Enum "None" , label is also "user Defined".

So when I am trying to fetch VASALtDlv record, the system is giving me None Record information as both labels are "User Defined".

help me how to rectify this situation so that system can take the label information in ENUm as type in table.

Thanks,

lakshmi

*This post is locked for comments

I have the same question (0)

All responses (6)

Answers (1)

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

Like (0)

Report

Hi Lakshmi,

If you have added the enumeration, you should also update the type in your new Role record.

Was this reply helpful? Yes No
Lakshmi Karambakkam 1,307 on at

Like (0)

Report

In my system, the type field is uneditable in the LogisticsLocationRoletable. So I am not able to change/edit it.

Is there any other way of editing it? In your AX instance, is it editable or uneditable?

Was this reply helpful? Yes No
Martin Dráb 237,990 Most Valuable Professional on at

Like (0)

Report

First of all, avoid using the same label for two enum elements. Users wouldn't be able to distinguish between them.

By the default, rule types created by users are "User defined" (LogisticsLocationRoleType::None). If you want different logic, you'll have to implement it. If users should be able to use both None and VASAltDlv, you'll have to give them a way to choose. If you want to always use VASAltDlv instead of None, what the advantage against simply using None?

Was this reply helpful? Yes No
Verified answer

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

Like (0)

Report

Hi Lakshmi,

The roles out of the box are created during installation and usually there is no need to change the type. If you now need another value, you could change it using a script or in the database. Probably you can add logic that it will insert a role with your type also during the installation/setup.

Was this reply helpful? Yes No
Lakshmi Karambakkam 1,307 on at

Like (1)

Report

Thanks Andre. Inserting through code was simple and effective solution. It worked out. thanks a lot.

Was this reply helpful? Yes No
Suggested answer

Community Member on at

Like (0)

Report

Just for completeness how to add a new system type for postal addresses, as I was also looking for the way in doing it here some further notes:

- Add new enum entry to LogisticsLocationRoleType i.e. CollectionLetterWPC

- under AOT\Resources\LogisticsLocationRoleData export the XML and put your new type in the exported file

...

<Item>

<Field IsTranslated="False" Name="Name">@SYS13960</Field>

<Field IsTranslated="False" Name="Type">CollectionLetterWPC</Field>

<Field IsTranslated="True" Name="Description">@SYS13960</Field>

<Field IsTranslated="False" Name="IsPostalAddress">Yes</Field>

<Field IsTranslated="False" Name="IsContactInfo">No</Field>

</Item>

...

- Import the changed xml in the resouce LogisticsLocationRoleData

- Create a new job to load the new value

static void createLogisticsLocationsRoles(Args _args)

{

;

DirDataPopulation::insertLogisticsLocationRoles();

}

- As last step. In case you don't like the Name you can change it using table browser on LogisticsLocationRole

Hope this helps

tom

Was this reply helpful? Yes No