I am working on the Calendar Board (FS300300) Classic UI screen in Acumatica 24R2.
This screen seems to be different from other screens because it does not support customization through Graph or DAC extensions, and the behavior of the screen is controlled mainly by the following page files:
-
FS300300.aspx
-
FS300300.aspx.cs
These files are part of the website source, and they are not compiled into the customization DLL. Because of this, when changes are made in these files, they work locally in the website, but they are not included in the customization package, and we cannot deploy them to another instance.
Also, this screen does not appear to have a Graph that can be extended, so the usual approach using Graph/DAC extensions cannot be used here.
I would like to know the correct and supported approach for this scenario.
Questions:
-
Is there a supported way to include FS300300.aspx / FS300300.aspx.cs changes in a customization package?
-
Can these files be added to the Customization Project → Files folder and overridden, or is this screen not intended to be customized this way?
-
What is the recommended approach for customizing Calendar Board Classic UI screens that rely only on ASPX / code-behind files?
Any guidance on the correct way to package and deploy such changes in 24R2 would be appreciated.
