on
RE:
Thank you for raising this idea post Layla.
RE:
Any updates on this? January 2025 and still no solution
RE:
I think, security concerns could be addressed in BC by implementing a check when adding a "Run As"-User ID into a job queue entry which ensures that the current user account has at least the permission scope that the "Run As"-User ID has. Such check already exists in the user account management area of BC e.g. whenever you add permission sets to a user account. You cannot give more permissions than you have with the current account/User ID.BTW: Seems that Dynamics Finance and Operations already has the possibility to define a "Run-As User ID" in the batch job management. Not sure how they handle the security topic, but you could surely find this out within Microsoft.
RE:
Interested in an update as well.
RE:
Related idea:https://experience.dynamics.com/ideas/idea/?ideaid=c4ce84e2-971f-ed11-b5cf-0003ff45dac8
RE:
This is a common requirement, not sure when Microsoft can improve and put priority on this part.Another common requirement is default order setting as per vendor, each vendor has their own order quantity preference.
RE:
For SOX audit purposes, 6 months as opposed to 90 days is even more ideal.
RE:
Seconding the post and comment. Our operations are hampered by this limitation and forcing us to find an alternative, which we don't want to do. We retain the data from our Customer Voice survey's and use it for comparative analysis. Increasing the limit by making it unlimited would significantly improve this product.
RE:
Hello, Is there any news on my recommendation for this issue? We are still having similar issues for this year!Best regards,Turgay Kayaer