Comments
+1 on this. Having the option to create a custom view and set it as default will allow admins to show only the email templates (Insert Email Template view) that can be used by specific groups. This will be easier than the current approach to control the hiding/showing of email templates via Type (Individual, Org) and Security Roles.
I agree with Wouter and Jaco !The BC Layout options (List, tall Tiles, Tiles) are already linked to the BC Views. When changing view BC knows the layout option. Is it a bad idea that the last selected view from the user is remembered and when opening the list page the last view that is used is openend instead of the "All" option...? This would make the last selected view option the default for reopening.
Are you aware that our Cepheo Software Solution Advanced Quality and Sample Management has had this feature for years? It also includes many other nice features like controlling individual license plates based on disposition codes, stability testing, multiple Advanced Quality orders per batch and many other things.Our automated transfer of test results to batch attributes and the brand new feature where you in a production facility can release finished goods based on quality work on the bulk product.You can see it on Microsoft Marketplace here: https://marketplace.microsoft.com/en-us/marketplace/apps?search=Cepheo&page=1And read more in depth articles about it and the setup on docs.cepheo.com Cepheo Quality and Sample ManagementContact Cepheo for more on this or any of our other smart modules and extension:https://marketplace.microsoft.com/en-us/marketplace/apps?search=Cepheo&page=1
I totally agree. We deal with organizations where people wear multiple hats all the time, and the current workflow logic just falls apart. It’s tough to explain to a client why the system is looping instead of just working. We shouldn’t have to keep building custom solutions to fix what should be standard functionality. A native fix for these dual-role and self-approval cases would be a huge win.
We have a similar requirement, and have many vendors that use a DBA company name. To solve this, we have added two new fields called Tax Name, and Check Name. This was functionality that we had used in our old Dynamics GP system, but created a customization in BC to handle. Not having the fields cause problems both for accurate TIN matching, as well as 1099 form generation and submission.