Introduction
The Epicor Kinetic web client is a powerful tool that allows users to efficiently access and manage company and site data. However, users have encountered a bug in the login process of Epicor Kinetic 2023.1.10, which results in the web client logging into the last company and site, regardless of the company and site parameters specified in the URL. This bug can cause confusion and potential issues with data access. To address this bug and ensure a consistent login experience, a temporary workaround is available.
Bug Description
When logging into the Epicor Kinetic web client, the system fails to recognize and utilize the company and site parameters provided in the URL. For example, consider the following URL: https://servername.epicorsaas.com/InstanceName/apps/erp/Home/#/home?company=CompanyID&site=SiteID
Even though the status line in the upper right-hand corner of the web client and the URL in the browser’s address bar indicate that the user is in a specific company and site, such as “Dallas Biz,” the web client may actually be accessing data from another company, such as “Huston LLC.” This inconsistency can be identified by the status line color not matching the indicated company, and it can lead to incorrect data being displayed or manipulated. Such errors can cause confusion and frustration for users.
Workaround
To address this bug, it is necessary to remove the company and site parameters from all URL bookmarks and shortcuts. By modifying the URLs to exclude these parameters, you can ensure that the web client more consistently logs into the correct company and site.
Instead of using URLs that include the company and site parameters, such as:
https://servername.epicorsaas.com/InstanceName/apps/erp/Home/#/home?company=CompanyID&site=SiteID
Modify the URLs to the following format:
https://servername.epicorsaas.com/InstanceName/apps/erp/Home/#/home
By stripping the company and site parameters from the URLs, you can prevent the web client from accessing incorrect data and ensure a reliable login experience.
Additional Considerations
It is important to note that this workaround is temporary and should be implemented until a permanent fix is provided by the Epicor Kinetic development team. Regularly checking for updates and patches from Epicor is recommended to stay informed about any bug fixes or improvements related to this issue.
Furthermore, it is crucial to monitor for any issues where the operating company and the reported company may not be congruent, as there may be other instances that cause this issue. Being vigilant and addressing any potential discrepancies will help maintain a consistent and accurate data access experience for users.