Microsoft Dynamics AX (Archived)

Combo box display/refresh issue

(0) Share

Report

Posted on by Tina Vyf

I am having exactly the same issue as this question (which, unfortunately, does not have a verified answer).

In more that three different forms, with four different enums, the combo box remains visible after a section is made.

This is after I selected a value and pressed tab:

3005.enum.jpg

If there is another field below the offending enum combo box, it remains visible behind the newly active lookup. Select first enum...

Move to next field, and the enum combo box remains partly visible:

What I've tried:

Restarted client
Deleted the UAC files
Cleared the caches (via Tools> Caches)
We noticed this a few weeks ago, so the AOS was certainly restarted a few times since then.

What I know so far:

More that one user experience this issue.
So far I have only seen it with enums, and not with other lookups.
Similar forms and enums worked fine in our R2 solution, but of course, the server, client etc is different.
If the form is resized or redrawn, the lookup disappears (as it should).
If I refresh the data source manually in the modified method (myData_ds.refresh()), the problem looks 'fixed'. But this does not seem like the neatest solution to me.

Any ideas what could be causing this issue and how I can solve it?

community.dynamics.com/.../142103

*This post is locked for comments

I have the same question (0)

All responses (11)

Answers (0)

5400 7,162 on at

Like (0)

Report
Copy link

Link copied!

Can you override modify field in enum control and write small code after super to test element.redraw().

Was this reply helpful? Yes No
Tina Vyf on at

Like (0)

Report
Copy link

Link copied!

Hi Bhaskar,

Thank you for your answer.

Yes, I've tried it and it is the same as my last bullet (calling myData_ds.refresh() does the same).

If I add this, the problem 'looks solved', but since it should not be nessasary to refresh or redraw manually, this does not seem like a solution to me.

This 'fixes' the symptom but does not address the cause of the problem.

Was this reply helpful? Yes No
5400 7,162 on at

Like (0)

Report
Copy link

Link copied!

can you check same enum in other new UI.

Was this reply helpful? Yes No
Tina Vyf on at

Like (0)

Report
Copy link

Link copied!

Hi Bhaskar, that is a really great idea!

I added the same datasource and field to a new form, and there it works fine.

I am going to keep on investigating, but I assume the problem is not with the enum, but with the form.

Was this reply helpful? Yes No
5400 7,162 on at

Like (0)

Report
Copy link

Link copied!

agreed it is not issue with enum. It is issue with Form Design any property or refresh.

Was this reply helpful? Yes No
Tina Vyf on at

Like (0)

Report
Copy link

Link copied!
I have tried quite a few things and I can 'fix' the problem:

By adding element.redraw() in the modified method on the form element.

By moving the enum field to another column (moving it to another field group is not enough, it has to be in a different column in the design).

If the problem was limited to one or a few enums, I would maybe consider the above options, but since I posted the question I have noticed the problem occurs with countless enums that are followed by lookups of other types.

I thought that this was some error caused by one of our customizations, but have just found it on the purchase order create form, where we have no modifications:

So, based on my latest findings my question is:

Why do many of the enum values that are followed by lookups of other types (like a date or table lookup), fail to refresh after selected? How can I fix this without creating a fix for every wrong enum lookup in the system?

Was this reply helpful? Yes No
Sohaib Cheema 49,492 User Group Leader on at

Like (0)

Report
Copy link

Link copied!

I cannot suggest you a solution for this as system is not in my hands. all I can, is, to offer you couple of steps using which you need to observe the issue

1) check if this is happening on all/majority of machines [each machine is refereeing to a separate installation of rich client ]

2) login on the same machine with different user id(s) and see behavior

3) check the kernel version and application version of client.

4) on any one of machines/client-installation try to update kernel to latest build.

Was this reply helpful? Yes No
Tina Vyf on at

Like (0)

Report
Copy link

Link copied!

Hi Sohaib,

Thank you very much for your answer.

This must have something to do with the client, server, .Net or operating system version.

It is luckily limited to all the environments on one server. This is our development server (Windows server 2008). I cannot reproduce the issue on any of our client's servers, who have the same version of our R3 solution, but have different hotfixes and all run on Windows server 2012.

We have updated the client, removed hotfixes that are not installed at our clients and updated .Net.

I assume that during some or other update this issue will be solved. If I find the cause I will post it, but till then the problem will be low priority since it affects us, but luckily not our clients!

Thanks for the help!

-Tina

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report
Copy link

Link copied!

Hi,

Do you have the solution for this?

I've tried all of the above, and from the link you have shared (https://community.dynamics.com/ax/f/33/t/142103)

but nothing has helped.

BR,

Nurdhiya

Was this reply helpful? Yes No