Comments
This can be partially solved with blocking rules on account status.and credit limit.The issue is that the originating sales order does not have a picking list generated and therefore the credit management checkpoints are not valid on the pick task.The credit checks are not done until the packing slip phase. This results in work being released to the warehouse for picking that will not be stopped until it is packed and cannot have the packing slip posted in the originating site.
This highlights an inconsistency in model-driven app behavior where lookup navigation is unintentionally restricted when grouping is applied. Allowing lookup columns to remain clickable, even in grouped views and would significantly improve usability by enabling users to organize data without losing quick access to related records. This enhancement would create a more seamless and intuitive experience across different view configurations.
This would be very very useable. The possibility to make fieldgroups more suitable for customers needs is imperative.Yes, you can add extra fields in an extension, but sometimes the field added is the most important info to have visible, and since we cannot alter the width of the dropdown (which by the way is super annoying) the least we should be able to do was to change the order of the fields (enable addfirst, addafter, addbefore) and the ability to hide certain fields in the fieldgroup WITHOUT having to mark them as visible=false.This has now been under review for a long time, and the subject is more than 6 yrs old. Wouldn't be time for MS to have a serious look at this one?