GENERAL
Announcements
- ★ Strategic shift in future BI development for ERP.net
- Version 2021 is now named "2022"
- 2020-09-23 Version 2020 RTM is here!
- 2020-09-17 System requirements for ERP.net Desktop Client 2020
- 23.08.2019 Changes in system requirements for EnterpriseOne version 2019.1
- The EnterpriseOne's documentation has a new address
SYSTEM RELIABILITY
- 2023-09-13 06:30 UTC Degradation/interruption of services in BG1
- 2023-06-22 19:30 UTC Possible temporary interruption of services due to scheduled maintenance
- 2023-02-23 14:00 UTC - Degradation/interruption of services in BG1
- 2023-02-23 20:00 UTC Possible temporary interruption of services due to scheduled maintenance
- 2023-01-17 16:30 UTC Slight disruptions
- 2023-01-12 20:30 UTC Possible temporary interruption of services due to scheduled maintenance
RULES
Released versions
TECH
What's new
- Document/Object Versions Handling (v. 2023.2)
- Calculated Attribute Inheritance (v.23)
- WMS: A new kind of policy - Require Product Scan (v.24)
- Auto start of J30903 Delete old document print images (v.24)
- New type of distribution of additional amounts "By Deal Type" (v.22)
- The 'Notes' field in the Sales Order panel of the Sales Order documents has been marked as obsolete and hidden (v.24, breaking change)
TECH BLOG
- ★ Better understanding of the hosting fee and how to slow down the growth of ERP instances
- How to use "Remoting Log"
- How to use "Exec Stats"
- How to use "Performance Benchmarking Mode"
- Full Domain Model documentation is now available online
- Simplified Version Numbering
TECH FAQ
- ★ Azure authentication
- ★ System Requirements
- Resolved: Error during an export of large reports to Excel
- Login ERP.net Desktop Client multiple users
- Fiscal devices supported by EnterpriseOne POS from 2019.1 version
- TeamViewer
DEV
DEV BLOG
- ★ Domain API breaking changes policy
- ★ Real time synchronization with ERP.net (v.22)
- All ERP.net websites now require a system (service) user (v.24, breaking change)
- Domain API: $filter by entity reference is now supported (v.23)
- OAuth client credentials flow: Scope argument can now be omitted (v.22)
- OAuth: the desired scopes must be specified explicitly (v.22, breaking change)