Issue Graph Type with Custom Screens after importing Modern UI

Any updates on this issue?

The fact that you’re getting a Modern UI ‘warning’ suggests that you’re working in 25 R1. I would not recommend working with Modern UI in 25 R1.

The same issue appears on the client’s 25R2 instance, exactly the same issues, excluding the warning, of course.

The fact that the Site Map does not display a Graph Type suggests something wrong with the TS files. Can you confirm the screen file contains @graphInfo (ie:

@graphInfo({
    graphType: "MyNamespace.MyGraph",
    primaryView: "MyView",
})

Have you tried modifying (or possibly deleting and recreating) the Site Map entry? The Site Map is extremely unstable in 25 R2. I’ve had so many issues with it. ​@Dmitrii Naumov - Will that be fixed in 26 R1?

Sure, the .ts file is defined properly and contains the graphInfo decorator along with the graphType and primaryView properties. As mentioned by the author of this topic, this customization works fine on other instances without any issues.

And yes, all the actions you proposed have been completed, but the issue persists.

So I cannot disagree with you that the Site Map is unstable in 25R2. Hopefully, a future version will resolve the issues, including the one reported in this topic.

​@darylbowman ​@aleksandrsechin 

when you say the Site Map is unstable in 25r2 are you referring to the Classic UI version of Site Map, the MUI version of Site Map or both? 

or are referring to how the data stored in the site map is used during screen rendering/execution and publishing?

We have a ticket with Acumatica regarding problems we are seeing where some part of the publishing/site map processing is defaulting to pulling information from the wrong tenant and causing all sorts of corruption in custom classic and MUI screens.

The problem was identified as an issue when there are multiple tenants in the instance.  

If there is only 1 tenant in the instance the problems do not seem to happen in initial testing.

Our issue is that the fix is not scheduled until 26r2 right now.  They are “hoping” that this will be fixed in 26r1SP1 which is coming out next week but we can’t get confirmation.

It seems to be related to linking screens to GIs and once the problem occurs, any custom screens fail with the View not found and other errors.  Attempts to resolve the issue produce messages like: the screen is not set up for MUI.

We’ve been struggling with this because we are primarily using an Acumatica SaaS instance and don’t have access to the server itself.  We also are at the mercy of other things going on in the environment that may be impacting our instance. 

There are many times where things behave differently between the time of day, amount of time since the last application restart/cache clear, etc.  Sometimes things have resolved themselves overnight.

What I’m trying to find out is:

Are other users of Acumatica where there are customization packages from developers involved are they seeing similar issues on 25r2SP1 for situations where there are new screens built in MUI? 

Do they have to have a Classic version of the screen in order to work? 

Are the users fully using MUI in their production tenants?

Any and ALL feedback would be appreciated.

The most glaring bug I found was that if you paste a Modern URL into a ‘Classic’ site map record, toggling to ‘Modern’ switches to a Classic URL. This may also be why you’re possibly encountering issues with having Modern-only screens. I started shipping this ASPX for Modern-only situations:

<%@ Page Language="C#" MasterPageFile="~/MasterPages/FormView.master" AutoEventWireup="true" ValidateRequest="false" CodeFile="ScreenID.aspx.cs" Inherits="Page_YOURPAGE" Title="Your Screen" %>
<%@ MasterType VirtualPath="~/MasterPages/FormView.master" %>
<asp:Content ID="cont1" ContentPlaceHolderID="phDS" Runat="Server">
    <px:PXDataSource ID="ds" runat="server" Visible="True" Width="100%"
        TypeName="yourNamespace" PrimaryView="DatesFilter">
    </px:PXDataSource>
</asp:Content>
<asp:Content ID="cont2" ContentPlaceHolderID="phF" Runat="Server">
    <style>
        .error-container { display: flex; align-items: center; justify-content: center; height: 80vh; background: #fff; }
        .error-box { background-color: #f5f7f8; border-radius: 6px; padding: 30px; text-align: center; }
        .error-box .title { margin-bottom: 16px; }
        .error-box .title__text { font-size: 20px; font-weight: 700; color: #EE4051; margin: 0; }
        .error-box .message { font-size: 16px; color: #1B1B1B; max-width: 400px; line-height: 1.5; }
    </style>
    <div class="error-container">
        <div class="error-box">
            <h1 class="title">
                <div class="title__text">Classic UI Not Supported</div>
            </h1>
            <div class="message">This screen is only available in the Modern UI. Use the 'Switch to Modern UI' option in the Tools menu above or set the 'UI' field to 'Modern' for this screen's record in the Site Map (SM.20.05.20).</div>
        </div>
    </div>
</asp:Content>

I’ve seen this several times as well. A ‘Reset Caches’ or ‘Restart Application’ (from the Apply Updates screen) has always solved the issue for me.