Welcome to the Sage X3 Support Group on Community Hub! Available 24/7, the Forums are a great place to ask and answer product questions, as well as share tips and tricks with Sage peers, partners, and pros from around the globe.
Our customer has requested can this functionality be reincluded, as not having a limit on the number of attempts to log in to X3 is considered a security risk.
Thanks
Sarah
Hi all,
Please support this idea if you are facing the same issue.
In X3 we have multiple types of Badges ERPFULL, ERPDIS, ERPMAN, etc. which we assign them to Roles > then Users via Group will be eventually assigned to a Role.
Issue: Assuming we…
In Sage X3, PU9, Common data Module>Products>Products(GESITM)
whenever I create a new product or modify the existing product, the data in description 2 and description 3 disappeared. ironically, the previous data in the same field for certain products…
Hello,
Some customers want to restrict the access of the function "Bank transaction management". Indeed, in multi-company cases, they want to display only bank statement for the company that the user is responsible.
There is no way to setup this access…
North America, Sage X3 & Sage Fixed Assets
Hello,
I'm new to my company and am in charge of reining in our Sage products. However, due to turnover and over-reliance on 3rd party support, I'm left in the dark on many things. I discovered recently that…
Please add the ability to audit changes to user records under Administration > Users > Users, specifically:
1. Changes to groups and/or roles in the user record;
2. Changes to passwords;
3. Failed attempts to log in, specifically incorrect password…
Hi All,
I am configuring a fresh X3 V12 copy on my system and while configuring Main Runtime, I am getting an error.
Can someone please guide me what am I missing? Much appreciated.
Screenshots are attached for your reference.
Hey Guys,
We are running Sage X3v7. We have 550 users in the AUTILIS table and 352 are set to inactive. I am contemplating deleting the inactive users but don't know what repercussions that might have across the database. One of the main motivators…
The logic would work as such, when the user gets disconnected from Enterprise for any reason, but their session remains active, when they attempt to log back into Enterprise, rather than receiving a message merely indicating them to have reached the maximum…
