Comments
Examples were not submitted correctly:tableextension 50000 "Customer ISV" extends Customer{ fields { field(50000; "Rating ISV"; Code[20]) { Caption = 'Customer Group'; DataClassification = SystemMetadata; } } keys { key(MonolithAppKey1 "Rating ISV") {} }}Before MoveApp Monolith: TableExtension Customer -> Field "Rating ISV" (+ declared as additional key)New App :After MoveApp Monolith: New App : TableExtension Customer -> Field "Rating ISV" (+ declared as additional key)
Yes, we do have a customer with 2 legal entities. All sales order goes via a sales company. Logistics is the second company. The small items are directly send to end-customer, but bigger items are send to a warehouse of the sales company for consolidation purposes (also items can be ordered at a vendor) for a one-time delivery. This is really required behaviour for the customer... without intercompany-relation this is possible, but then we miss the intercompany benefits...
The ability to block variants at register is essential. Variants/Colours/materials/ingredients can differ between variants and if any of these are reported to be toxic or contain unlisted ingredients (nuts) the whole product needs to be blocked instead of just the specified variant. Please implement this.
We have the same topic with item requirements and posted project transactions. Please fix it. It's weird to say: here, we give you the option to save views, create tiles, use advanced filters... promote it as the way to go for users to 'design' their daily work to be effective and efficient and then go back and say: but only in certain cases. Many cases won't work. Sorry. It's dissatisfying.