You’re offline. This is a read only version of the page.
I noticed some unexpected behaviour on the web client of Microsoft Dynamics NAV 2015 (v8.0.38457.0).
The classic client - on the other hand - bahves exactly as expected.
The issue:
There is a ListPart (Sub)Page that has 'show as tree' set to 'Yes'. 'DeleteAllowed' is also set to yes. The tree structure has two levels.. let's call them 'level 0' and 'level 1' for now.
On the classic client, we are free to delete any 'level 1' record, and we can delete 'level 0' records as long as they don't have any 'level 1' records attached.
On the web client the user interface seems to suggest that we can do exactly the same things we can do on the classic client (delete any 'level 1' records and delete 'level 0' records as long as they are empty), and eventually we can. But after opening a new page and opening the drilldown menu, clicking the 'delete' button doesn't result in any action being taken. After closing the drilldown menu and opening it again, we can delete the line without problems.
From what I found out the issue seems to be related to whether the first line in the subpage can be deleted. If the first line can be deleted (that is: if the first line is an empty 'level 0' record), then there is no problem at all. If - however - the first line can not be deleted, then the button for deleting a line is also non-responsive for other lines.
Has anyone heard of this issue before? is it a bug? is there a known fix or workaround?
*This post is locked for comments
Hi Daniel,
I have not come across the scenario and not sure about the similar fix in latest CU...
However as MS is working on lot of enhancements (specially for Web client), based on the various feedbacks around the world, I believe lot of problems are getting resolved when it comes to platform upgrades with latest CU / versions.
Can you share the sample page number, where you are facing such issue, so that I can check in my development environment? I already have latest NAV DB available with me.
Regards,
Vishal Salot
Vishal:
Upgrading to NAV 2016 is probably not really an option considering the current scale of the project.
I'll consider checking with NAV 2015 CU16 once we have some time to do a proper backup and testing for that.
Do you happen to know if there is a related known issue that has been fixed in CU16?
Alexander:
I get the same result with Firefox, Chrome and Internet Explorer.
I haven't tried any other browsers, but I would expect the same result.
Have you tried to use a different web browser? Would it give you the same result?
Hi,
I would suggest to check the working of the same in latest NAV 2015 CU16 or even NAV 2016 Cu4 release in test environment.
Regards,
Vishal Salot
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
#1
André Arnaud de Cal...
291,253
Super User 2024 Season 2
#2
Martin Dráb
230,188
Most Valuable Professional
#3
nmaenpaa
101,156
Share
Report
All responses (
Answers (