web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Microsoft Dynamics AX (Archived) / Two users, same securi...
Microsoft Dynamics AX (Archived)

Two users, same security groups, different results...

(0) ShareShare
ReportReport
Posted on by rlem 234

There are 2 users with identical security groups, but one of the users can no longer add lines to a new PO.  I had deleted their AX account and recreated it recently.  Since then, they have been unable to do this.

Any ideas what could cause this?  Thanks a lot!

*This post is locked for comments

  • Denis Patrakov Profile Picture
    Denis Patrakov on at

    So now both of the users can't add lines to a new PO, right? Try creating a new test user and assigning it to the same security groups. Check if that user will be able to do all the necessary (or expected) tasks.

  • rlem Profile Picture
    rlem 234 on at

    Actually no, and that's what has been driving me so crazy!  Is there a best practice for truly recreating an AX account from scratch?  Oftentimes when I have a problem with a user account, I remove the local AUC file so AX recreates it upon restart.  If that doesn't work I find that deleting the user from AX itself, and recreating them exactly as they were can fix.

  • Verified answer
    Denis Patrakov Profile Picture
    Denis Patrakov on at

    Access rights in AX are assigned to groups, not users, so that recreating a user should not actually impact access rights settings. But when you recreate a user in AX, you should either assign a different userId or cleanup the SysLastValue table records for that user (it should be done automatically upon user deletion but I'm not sure about that). Actually SysLastValue cleanup can solve lots of problems without having to recreate a user account in AX. Local application cache (AUC files) usually only causes problems if you change something in the application without forcing users to close all their sessions and then login to AX again (if you have more then one AOS then sometimes it's necessary to restart them all).

  • rlem Profile Picture
    rlem 234 on at

    I thought about using a new user ID, but the problem is our naming convention is cryptic and if we ever needed to "look up records" on who modified data, that user ID would no longer be in the users table making it very difficult or impossible to find out who the ID was associated with.  For this reason I always reuse the same ID when recreating a user.

    I will look into SysLastValue cleanup.  Never heard of it before and it sounds like a cleaner solution.  It sounds to me like removing the AUC and using this SysLastValue cleanup might be just as effective as creating a new user from scratch.

    Thanks a lot for your help.  I will verify your answer once it's resolved.

    EDIT:  I found a lot of information out there about SysLastValue, but nothing about how to actually use it for cleaning up a user.  While I continue looking, are there any good resources or guides you know about?  It would be nice to know of any repercussions or dangers of doing this.  Thanks!

  • Denis Patrakov Profile Picture
    Denis Patrakov on at

    Lots of application objects (classes, forms, reports, etc) store some kind of information in SysLastValue. In case an application object was changed (especially classes - RunBase descendants), previous settings saved in SysLastValue might become a source of a problem, like in the topic Error on opening 'Consistency check' form. The kernel also stores user's form setup in SysLastValue, and sometimes it can lead to a form design distortion.

    In case you delete all SysLastValue records for a particular user, the latter can lose a lot: auto report settings, custom form setup, saved queries, etc. But if some part of your AX application works fine for all users except one, you can actually try deleting SysLastValue settings only for that particular part (class, form, report...) and for that particular user. Well, of course SysLastValue cleanup should always be performed on a per-user basis - unless you upgrade to a new AX version.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Season of Sharing Community Challenge Winners!

Congratulations to our community stars!

Women in Power Builds Momentum

Expanding mentorship, skilling, and AI innovation

Congratulations to the September Top 10 Community Leaders

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics AX (Archived)

#1
Prashant Singh Profile Picture

Prashant Singh 2

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans