Comments
I also recognise and support this idea, especially for vendor approvals, where this comes through regularly in colleague and customer feedback.It seems more efficient and safe to prevent a vendor/customer/item being used until it's approved, or at least offer that option. You could argue that the likes of Purchase Document approval workflows are a way to prevent e.g. PO's being released before vendor approval, but this still allows the user to spend time preparing a PO before realising it can't be sent to the vendor (yet), and you're relying on approver(s) to know that the relevant vendor hasn't been approved yet.
This does not make sense for a developer option as most ledger pages are affected. Microsoft needs to determine whether searches make sense on ledger pages versus master lists. Same is true when turning Analyze on for many list pages.Rather than go into what looks like a freeze, a warning that at times filtering is a better option than Search would be informative.Could then make a case that a warning based on numbers of records involved is helpful to inform the user, or default search to page contents only may be kinder