User Group - Drop Down

(0) Share

Report

Posted on by SU-22040800-0

2,459

I have an strange issue on all my users not using Terminal Server (i.e. the AX client is installed locally - Win10). When they go to GL - Setup - Ledger Calendars, and click on the drop down button to show the list of groups, it does not show the list... However if I type in the group name, it validates and accepts it.

I'm not sure if it is a dot.net issue possibly..? Or if there are other components not installed.

Anyone else experience this ?

User on the TERMINAL SERVER:

Same User on their local installation:

*This post is locked for comments

I have the same question (0)

All responses (17)

Answers (2)

Community Member on at

Like (0)

Report

Similar issue with AX 2009, we just uninstalled and reinstalled asp.net 3.5 from windows features.

Was this reply helpful? Yes No
SU-22040800-0 2,459 on at

Like (0)

Report

Thanks for the response Glen

Unfortunately it did not resolve the issue..

Any other ideas?

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Have you tried using AX Tracer to see if it calling the default lookup method for the dropdown for that user session? I know its a pain to run the AX Trace parser but it can sometimes fine the odd things like this and shed some light.

Was this reply helpful? Yes No
SU-22040800-0 2,459 on at

Like (0)

Report

hi Glen

thanks for the response.

I managed to get a trace going, but am not sure what I'm looking for.. would you be able to assist? I've attached some screen shots below:

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

On your trace, that captured just the load of the form and click of the Ledger Calendar? not sure if it is possible but could you attach the trace log. I can review it. Also create a trace log of it on the TS and the client with the exact same actions.

1) Open form

2) click the dropdown.

If you can do that I will see if we cant find a reason why it isn't loading.

Second Question I have is this the only dropdown that isn't working(That you know of)

Was this reply helpful? Yes No
Javirrubio 965 on at

Like (0)

Report

Maybe stupid suggestion but I would start removing user's usage data and auc files in the local computer as well as in the Terminal server

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Usage data shouldn't affect the dropdown, but the auc file could be corrupt.. If that is the case I would also shut down your AOS and remove the AOI files so AX will rebuild the code base on the next service startup.

It isn't a stupid suggestion, sometimes things like this do get fixed by removing the cached code.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Hi Javier,

I am helping James with this issue, he just isn't able to respond at the moment.

The users local computer has a fresh instal that has never been logged onto before.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Hi Glen,

I have ran the trace for James and the results of the trace on the server (which is a installation where the dropdown works) are on the following link;

http://filegooi.co.za/get2/4ef72f22b1e7ca3ce8333f28d93c99cd/Server+2nd+Trace.etl

The below is the trace on the client (where the drop down does not work);

http://filegooi.co.za/get2/d556818dc0a579e572ce04d67b10f8f6/Client.etl

The trace was ran as follows:
1. Start the trace on the Trace Cookpit.
2. Click Ledger Calendars
3. Click on the dropdown arrow on the Ledger Colum.
4. Stop the trace.

To answer your second question, yes this is the only drop down that users are not able view. The other drop downs e.g. Customer Group work perfectly.

Do you know of another User Group dropown in AX that we can use to check whether the issue exists on the screen or on the drop-down itself?

Was this reply helpful? Yes No
Verified answer

Mattias Irveland 40 on at

Like (0)

Report

Hi James,

We just found out that we are are experiencing the same issue. Our workaround is to do montly closings etc on remote servers with older OS.

In CU12 or CU13 Microsoft changed the Form design Style from Auto to Lookup, and that makes the lookup work on Windows 10 clients. Perhaps you're running on a older version and can solve it with that small change?

We are running CU13 but we changed the Style from Lookup to Auto in order to solve another issue where the lookup for selecting additional tables to join, in advanced filters, is placed in the upper left corner of the screen while not being re-sizable. Obviously, we'll have to create a MS ticket for that now.

Hope it helps,

Mattias

Was this reply helpful? Yes No