Sage 200 UKI Ideas Portal
It would more helpful to have the parent SysFeatureAreaLoggingID recorded against child forms
Without it, we cannot do a query that joins child forms to parent forms
| Idea Benefit | We are currently trying to track problems between POP and P/L invoicing - so we want to identify all instances of Sage.MMS.POP.PostPurchaseInvoicesForm where there is no related instance of Sage.MMS.PurchaseLedger.PostPurchaseBatchInvoiceForm |
| How do you solve for this problem today? | Run a query to find the POP form, then restructure that as a time based query to try an see if the child form was logged |
| Product Variant | Sage 200 Professional |
The "solution" we currently use is only applicable after finding a known instance of the POP form being opened.
We are then forced to examine the following rows visibly and jump to conclusions
If the user if processing multiple POP invoices then we probably would not be able to reach any conclusion, given there is no link between child and parent form entries in SysFeatureAreaLogging
It does not allow us to do a general query were we can find all instance of the problem automatically