Web API allow Purchase Orders to be booked in / received
Expand the Web API functionality to allow confirmation receipt or booking in of purchase orders. For example, allow external apps or warehouse systems to confirm goods received, the batch/serial items, and the locations being book into.
Andrew Watts
18 days ago
in POP
0
Idea Accepted - Gauging Support
Reduce The Number Of Records In The tblAudit Table
Over time the tblAudit table within the Sage200Configuration database can grow to be an unmanageable size. Within System Administrator it would be helpful if there were an option to be able to only keep entries which are x days old. Ideally this w...
Alison Alison
almost 2 years ago
in Event Logs
2
Idea Accepted - Gauging Support
When reviewing what has happened via SysFeatureAreaLogging in would be very useful to have an additional field that stores the primary reference for the related action e.g. for Action "Sage.MMS.SOP.ConfirmDespatchForm" the SO No field could be added
Andrew Dunn
about 1 year ago
in Event Logs
9
Idea Accepted - Gauging Support
Sage 200 Standard Online Automatic Match & Close PO's
Like for Sage 50cloud and Sage 200cloud, the API of Sage 200 Standard Online should also cater for Automatic Matching and Closing of Purchase Orders. A basic feature of any Sage complementary software that is not available in this version of Sage ...
Guest
over 5 years ago
in POP
0
Idea Accepted - Gauging Support
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
Andrew Dunn
about 1 year ago
in Event Logs
1
Idea Accepted - Gauging Support
Following on from Add Reference, it would also be really useful to have the SessionInfoID (as per the config DB) as per of the logged data We see data inconsistency problems usually related to uses doing an action and reversing it multiple times (...
Andrew Dunn
about 1 year ago
in Event Logs
0
Idea Accepted - Gauging Support
Split the Sage 200 System Event Logs into Daily Files for Troubleshooting and Archiving.
Split the Sage 200 System Event Logs into Daily Files for Troubleshooting and Archiving. At the moment theSage200SelfService,Sage200SecuredServices,Sage200Services are cumulative, are the only file in each of these folders and can grow to GB's. Ca...
Jeff Smith
about 6 years ago
in Event Logs
0
Idea Accepted - Gauging Support