Renamed namespaces for multiple entities in system (v25, breaking change)

In Version 25 of ERP.net, we have completed the renaming process of entities (Entities). This initiative began in Version 24 with the "root" entities, and now, in Version 25, we have finalized the task by renaming the subordinate entities.

Summary of Renaming:

• Version 24: Renamed 63 entities

• Version 25: Renamed 50 entities (the current batch)

We do not plan any further large-scale renaming efforts. This is a definitive completion of the process. While we understand that this may cause challenges for external applications, the renaming was necessary. Any future renaming (if any) will be on a much smaller scale.

Timeline 

This announcement is being published several months before the official release of Version 25.

The goal is to give our customers and partners ample time to prepare.

Documentation - full renames list

As with the previous renaming process, we have provided comprehensive documentation on the renamed entities. This time, we have further refined the documentation by resolving minor issues, ensuring an even better resource for your reference.

For detailed information about the renaming process, please visit: https://docs.erp.net/model/reference/renames.html

User Business Rules and Calculated Attributes will be automatically updated

During the database upgrade to Version 25, the new entity names in business rules and calculated attributes will be updated automatically.

This spares our customers and partners the effort of manual adjustments, as no additional actions are required for this transition.

What do you need to do then?

As is standard before a major release, it is necessary to verify if the external applications going to be functioning correctly with the upcoming changes and to make adjustments to them (if necessary).

Here you can read more information about the impact on external applications and recommended actions - https://docs.erp.net/dev/domain-api/common-tasks/handling-renames.html

We strongly recommend that, if possible, applications be made compatible with both versions 24 and 25 by incorporating version checks. This approach will eliminate the need for meticulous synchronization of updates between ERP.net and the applications.