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 :
Microsoft Dynamics AX (Archived)

Identifying source of a journal block

(0) ShareShare
ReportReport
Posted on by 70

Working with AX 2012 R3, we've seen instances of the Cash and bank management > Journals > Bank reconciliation form showing journals as In use with the Blocking tab identifying the Used by user as a user who has no permissions in the Cash and bank management module.  Those users who need to access the journal have been able to clear the block, a conclusion reached elsewhere, but I'm curious if anyone else has seen this behaviour, and if so, what you've done about it.  I could turn on database auditing for \Tables\BankReconciliationHeader\Fields\InUseBy, or go further & put an insert/update trigger event handler on the field to custom-capture a stack trace, but that feels like it might be overkill.

I can see the In use checkbox displays a method on the form datasource that calls \Classes\BankReconciliationHeaderFormView\inUseBlockReconciliation, which calls \Classes\BankReconciliationHeaderViewModel\dsReconciliationMethodInUseBlock, ultimately referencing \Tables\BankReconciliationHeader\SessionId, so I can see when the relevant user session started or ended, which allows us to have more confidence that the blocking user hasn't had their roles changed recently, so their ability to access journals hasn't changed since they apparently blocked the journal.  If it wasn't for the fact that both the SessionId and InUseBy fields live directly on the header record, I would wonder whether re-use of a session ID could lead to the Blocked by field showing the wrong user, but I don't think that theory holds water.

Any thoughts welcome. 

*This post is locked for comments

  • Verified answer
    André Arnaud de Calavon Profile Picture
    307,765 Super User 2026 Season 2 on at

    Hi RichHims,

    The SessionId field can indeed cause a wrong user name shown as person who blocks the journal. This can be caused if the session was killed by the user or the system. If then another new user will get the same session ID, it will find this user instead of the one who had the journal in use before.

  • RichHims Profile Picture
    70 on at

    André,

    Thanks for that.  I ruled out that idea on the basis that the table field InUseBy name & data type suggests it will hold the user ID of the user who has the journal in use, but you've made me revisit & I see that the form datasource method populates the user-visible control using the SessionID.  Hence, the InUseBy field appears somewhat redundant...  Appreciate you completing the picture where my incomplete knowledge led me to discard the 'obvious' stale pointer theory.

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 August Top 10 Community Leaders

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics AX (Archived)

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans