Comments
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.
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.
In NAV and older versions we used to have filter option | to add additional values from the list, but in BC it is not possible to do so. Let's say we have three vendors in the list - V0001, V0002 and V0003. And in the report in older versions we were using filters V0001|V0003. In BC however, if I select V0001| and trying to add V0003 - it overwrites previous value and leaves just V0003.Would be nice to have that filter option back!