Yo yo yo! DynamicsDad here, ready to chat about something we all might wish we could ignore but really shouldn't, session inactivity timeouts in Dynamics 365 Finance & Operations.
How to Tweak The Timeout Parameter
To change the value, follow these steps:
Select System administration > Setup > System parameters to open the System parameters page.
On the General tab, in the Session management section, enter a value in the Session inactivity timeout in minutes field.
Select Save.
If you set the value to greater than 30, you will be prompted to confirm your selection. The confirmation prompt says "Increasing the inactivity session timeout can cause extra load on your system, which can lead to a decrease in performance. Are you sure you want to continue?" The higher the value, the higher the load will be, which can affect negatively system performance. Select Yes to save the changes, or No to revert to the existing value.
Why Not Just Set It to 60 Minutes and Forget It?
You might think setting your session timeout to the max is like giving yourself a long leash. But here’s the catch: It’s like leaving your front door open while you pop over to the neighbor's house. Sure, you might be right back, but what if you’re not? A lengthy timeout can lead to unauthorized peeks at your data if someone else strolls by your unattended workstation. Not so great for data security, right?
The Trouble with the 5-Minute Timeout
Setting your session to timeout at 5 minutes? Prepare for some eyebrow raises and maybe a few groans if you're running a report that’s slower than a snail on a lazy day. By the time you fetch your coffee, your session could be as gone as the dinosaurs, taking your unsaved work with it.
Syncing with Your Device Lockout—Keeping Things Tight
Here's a tip straight from the DynamicsDad playbook: sync your Dynamics 365 session timeout with your device’s lockout period. If your laptop locks after 15 minutes, why let your Dynamics session hang out any longer? It’s about keeping your fort secure while not making your life harder.
Custom Logging for Session Timeouts
Logging these events is crucial for monitoring user activities and maintaining security protocols. By capturing data on session timeouts, you can analyze user behavior patterns to determine if the current timeout settings are adequate or if they need to be extended to better suit operational needs. This analysis helps maintain a balance between security and user convenience, ensuring that compliance standards related to data access and user activity are met.
But how? You can extend D365 to log when users are logged out due to inactivity by creating an event handler or chain of command into that class and put that data in a new custom table. Don't forget a simple list page and basic security for that new form though.
Quick Pro Tips for Handling Long Running Operations
When you’ve got a marathon task, consider using Dynamics 365’s batch job framework to run it on a batch server, effectively avoiding any session timeouts. Alternatively, utilize the SysOperation framework for asynchronous processing, letting your heavy-duty tasks run smoothly in the background without session disruptions.
Dad Joke of the Day
How can you tell it’s a dogwood tree? By the bark.
DynamicsDad
Comments