I have Acumatica 2023R1 Custome Project product, if i will update acumatica 2023R2 or 2024R1, Do I have to recode All my custome screens or not?

Hi @Febri 

No you shouldn’t have to recode all your custom screens.

However, with 24R1, there was an update to DAC’s in which they now must contain PXBqlTable alongside IBqlTable, if you upgrade an instance, you can try to publish the customisations and check the errors that you get, if any.

Aleks

Hi @Febri ,

As @aiwan  mentioned, In most cases, you will not need to recode all your custom screens when updating from Acumatica 2023 R1 to 2023 R2 or 2024 R1. Acumatica generally maintains backward compatibility for custom projects across minor and major version updates. However, some adjustments may be required due to:

1. API Changes: Review the release notes to check if any API changes affect your customizations.
   
2. New Features or Enhancements: New functionality in Acumatica may introduce conflicts or new methods that impact your custom screens.

3. Attribute or Field Modifications: If Acumatica has altered certain DAC fields or attributes, your customizations might need minor adjustments.

Test your custom project in a local environment for any compatibility issues.

Hi @Febri 

When upgrading from Acumatica 2023 R1 to 2023 R2 or 2024 R1, you generally do not need to recode all custom screens. Acumatica's platform is designed to support customization compatibility across versions. However, there are some key considerations and potential adjustments you may need to make depending on the changes in the new version.

Review the release notes for 2023 R2 or 2024 R1 to identify any deprecated features or changes in the platform that may impact your custom code. Occasionally, Acumatica may change or remove specific methods, DAC fields, or attributes that custom projects rely on.

In the Customization Project Editor, after upgrading, you should re-publish and validate your project against the new version to identify any issues.

You may find some minor changes or adjustments needed for compatibility (e.g., updates to DAC fields, changes in BQL syntax support, or slight adjustments to event handlers).

If your customization includes workflows or uses APIs (like REST or Contract-Based APIs), verify that endpoints, workflows, and custom actions are still compatible, as some of these areas may have updates between major versions.
As @aiwan suggests, in 24 R1, Every DAC must contain PXBqlTable alongside IBqlTable. 

Release Notes for 24 R1

Hope, it helps!

This My Error

My Custome Custome Screen and New Screen

I have found the code to call this.
so what is the replacement for all of this?
or where should I read it

using SiteStatus = PX.Objects.IN.Overrides.INDocumentRelease.SiteStatus;
using LocationStatus = PX.Objects.IN.Overrides.INDocumentRelease.LocationStatus;
using LotSerialStatus = PX.Objects.IN.Overrides.INDocumentRelease.LotSerialStatus;
using ItemLotSerial = PX.Objects.IN.Overrides.INDocumentRelease.ItemLotSerial;
using SiteLotSerial = PX.Objects.IN.Overrides.INDocumentRelease.SiteLotSerial;