on
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
RE:
Yes this would really be useful. After a while workspaces accumulate, and within every workspace many files. Opening an old workspace you have no clue what everything is meant to do.A quick workaround is creating a notebook called 'readme' but support for proper markdown would be ideal.
RE:
It seems like adding this to the app should be fairly straight forward given the functionality already exists in the workspace view.