Modern UI Issues

I think the big one is the removal of tabs on GI filters. This change was not good.

I also struggle with the import scenario builder in modern UI. I have to toggle between the two UIs to find fields, and it takes much longer to build them than they used to. 

There are also quite a few bugs. Here are a couple to start…

1. Can’t rearrange parameters and conditions in the GI editor anymore.
2. Export to excel for GIs is still broken
3. Performance seems to decline on screens/GIs using modern UI

Missing things

1. Shared configuration for grids not available.
2. Opening a screen from a list (link not side panel) returns you to the first page of the list when you close the screen.  Go to a page 6 of the stock items and click the inventory ID to open the stock item maintenance.  Close the stock item screen and you are back on page 1.
3. Right click to insert row in a list or a GI definition
4. after publishing a customization and restart the Screen is Loading message seems to take a much longer time.
5. Cannot report time on the Labor screen in MFG by typing 130 for 1 hour and 30 minutes.

The ‘Upload using mobile app’ button doesn’t work on the Purchase Receipts screen, however it works when switching to Classic UI

25R2 version:

1. We create Opportunities and put the Details of the order on the Details tab.  We then click the Create Quote option from the … menu. This brings up the Create Quote dialog box that has two tabs – MAIN and USER-DEFINED FIELDS.  We leave the default values on the MAIN tab and put the Product Line in on the USER-DEFINED FIELDS tab.  When you go to the USER-DEFINED FIELDS tab, it shows the Name of the UDF “Product Line” and the Value of the UDF.  How this works is the initial Value is empty and you click into that field and pick the Product Line from the dropdown menu.  However, the Value field is NOT editable.  It does nothing when you click or double-click in it.  This works fine in the Classic UI.  
2. Click on File icon on any screen and click Edit to see the Versions.  We have many versions of files from our Export Scenarios.  We go out and clean these up to just leave a few days.  The view shows one page of versions (around 13 or so).  If I click the > arrow key to go to next page, it shows the message “Nothing has been found”, the screen is blank, and the arrows for moving forward or backwards have disappeared.  This works fine in the Classic UI. 
3. Mentioned above, but I agree that you can’t order Parameter and Conditions in an GI editor anymore.

bump

The biggest issue I have in Modern UI is not being able to add lines in the middle of a project quote.

This is an absolute necessity. Otherwise we have to add lines at the bottom of the quote and then drag them up.

It is already described very well here:

Modern UI: Bring back right click context menus | Community

Thanks for giving us the opportunity to share our thoughts and ideas.

The Modern Customization Project Browser displays the current project name NOWHERE

The usability of the ‘Modern UI Editor’ is so confusing (in my opinion) that it will deter people from making simple customization changes themselves (which is actually great for my business):

I just found this one…

Hidden parameters now take up real estate in GIs

Edit: Changing the arrange parameter field to 1 instead of 3 seems to fix the issue. 

This post looks relevant to this discussion:

Customer struggling to export/move a Pivot for a GI between environments.

I’ve been having issue with migrating GIs now. It used to be that the inquiry title and screen IDs were the only validation when migrating GIs to a separate tenant. Now, when migrating GIs, you can’t simply change the inquiry title and screen ID and then migrate the GI like we used to be able to do. 

Inquiry validation seems to be based on NoteID now. So if the same NoteID exists for an inquiry in the tenant you are copying to, the GI import is going to erase that GI with the same NoteID.

In order to migrate a GI now, you have to Copy and paste the GI in the “From” tenant so that is generates a unique note ID, then you can migrate the GI over to the “To” and not erase the GI with the same NoteID.

As far as I know, that’s not new, at least if you’re dealing with XML Import/Export.  DesignID (Which is I think the database field that you’re referring to as NoteID) has been the primary key for imports via XML for awhile.  I keep getting caught out by this.

If you’re exporting/importing, another option is to just modify the DesignID GUID in the XML to force uniqueness.

I remember opening up the XML in notepad and changing the screen ID when there was a conflict a year or two ago. I never had to worry about the NoteID/DesignID  up until recently. It was always the Screen ID that the XML import would complain about, but it could be that I may have missed this error.

I thought the NoteID was a GUID and that makes them unique..  A best practice, and not always followed, is to change the screen ID when you publish to something unique to the client or partner.  For example, if the client is Jones, then make the screen id JO.NE.xx.xx

This is also a known issue:

26 R1 Generic Inquiry sorting bug? | Community

Email Activity screen will not accept multiple images.  When pasting in a new image, the first image becomes a copy of the second image.  When I switched the screen to Classic, the user was able to add two screenshots to the email body with the same technique that was confounding her in Modern UI.

We have run into several of the above mentioned issues, and have reported others via cases. I am hoping that this thread is being actively monitored by those who are deciding that 26R1 is truly the last version to allow a roll back to WORKING classic interface functionality. Those become quite difficult to explain to clients when we have to roll back, and will become worse when there is no roll back possibility. I can envision the clients saying - you encouraged (forced) me to upgrade and now XX number of screens no longer work as well as they used to.

The GI formula builder in the generic inquiry editor has some issues...

1. We can’t resize the formula box, so we can’t expand the visibility for long formulas.
2. Can’t use “returns” anymore in the editor. While not a functional key, being able to add spaces between parts of the formula when building a formula has been extremely helpful for me in the classic UI.
3. Inserting a field into the formula builder will now insert the field randomly, not where the insertion point/marker is as shown below.

Thank you for the reminder ​@bwhite49  - yes the GI editor has taken a turn for the worse. Buggy entry within the formula screen, and we also can not just edit the formula on the main Results grid. Similar issues with import scenarios and finding the correct object.

I have not seen anybody complain about the dashboard filters yet. Does anybody find the change “helpful?”

I have a feeling they are going to add this everywhere, and I am a little worried. It looks cool, but it’s hard to know what to do. Adding brackets is not intuitive at all. 

Thank you ​@DavidEichner for starting the discussion and everyone here for contributing! I wanted to let you know that the content of this post went to Jon Pollock and Engineering this morning at his request. They also have the link to this post for any further that is added. 😁

Most of the feedback from our internal users and our clients involves not liking the way the data fields are more spread out requiring users to have to page down and up to see the entire tab screen.

Why does 26 R1 build-tools prevent screens in /src/development/ from building 'includes'? | Community

Not sure if this is a Modern UI issue, but we are unable to extend customer to vendor using sales demo data. But when extending to vendor for the same customer in classic UI, the record converts as expected. This is the error we are getting: 

Please provide build info when reporting the issue. Worked in  Build 26.100.0175.1 

Converted to Vendor this customers

Related seeming posts:

Relative date parameters no longer working for user in Modern UI (@YearStart, @WeekEnd, etc) and returning nulls when called as part of report default values.

Similar issues in ARM with parameters in Modern UI differnt from classic UI and not available with MUI on: