Disable Action Button on Lazy Loaded screen error

What version of Origam are you using…
I upgraded to 2025.10.5.4235 (from 2025.5.2.3862)
I was trying to open screen with action buttons disabled

I was expecting it will work as the bug should be already fixed
https://community.origam.com/t/disabling-action-buttons-in-lazily-loaded-screen/4396

Instead I’ve got error

2026-09-02 09:13:46,891 [51] ERROR Origam.Server.Controller.AbstractController - The root section with the root entity can’t have action buttons disabled.
System.Exception: The root section with the root entity can’t have action buttons disabled.
   at Origam.Server.UIManager.FormXmlPostProcessing(UIResult result, DataSet data, XmlDocument formXml, UserProfile profile, Guid workflowId, DataStructureSortSet sortSet) in D:\a\1\s\backend\Origam.Server\Common\UIManager.cs:line 308
   at Origam.Server.UIManager.SetFormXml(UIResult result, UserProfile profile, SessionStore ss) in D:\a\1\s\backend\Origam.Server\Common\UIManager.cs:line 268
   at Origam.Server.UIManager.InitUI(UIRequest request, Boolean addChildSession, SessionStore parentSession, IBasicUIService basicUIService) in D:\a\1\s\backend\Origam.Server\Common\UIManager.cs:line 223
   at Origam.Server.Controller.UIServiceController.<>c__DisplayClass10_0.<InitUI>b__0() in D:\a\1\s\backend\Origam.Server\Controller\UIServiceController.cs:line 129
   at Origam.Server.Controller.AbstractController.RunWithErrorHandlerAsync(Func`1 func) in D:\a\1\s\backend\Origam.Server\Controller\AbstractController.cs:line 117

The original bug was the fact that the engine didn’t return correct error message. Instead of referring to action buttons it complained about missing default sort.

We have fixed the error message, but opted to not to change the engine behaviour. So what you’re reporting is the intended behaviour at the moment.

There must have been some change in behavior, because everything worked without any errors in version 2025.5.2.3862. In version 2025.10.5.4235, an error with the action buttons appeared. It’s not just about changing the error message.

I think the issue is in this change:

You’re right. I see it now that the change actually weakened the condition. We’ll implement the fix.

Thank you! Please could you implement the fix to version 2025.10.5.4235. If the behavior will return, then this issue https://community.origam.com/t/field-from-used-sortset-not-exist-on-screen-section-panel-error/4650 should be hopefully resolved as well.

We will release 2025.10.6. It is not possible to amend the existing release.

I also suspect that it could solve the other issue as well.

2025.10.6. will be perfect. It would by great if you could release the patch by end of this week so I wouldn’t have to roll back the all the instances to the previous version.
Thank you!

Here is the pre-release version with the fix. If you confirm that it is working for you, I’ll make it official.

Edit:

Link to commit fixing the issue: Reverting pr #4138 · origam/origam@8966760 · GitHub

This fix works as expected. The screens are loaded as usually. You can make it official.
Thank you!

Just to make sure, the fix also solves Field from used SortSet not exist on Screen Section panel error?

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.