To have a Validate All button on the 50 to 200 migration tool
When moving customers from 50 to 200, if a customer has a financials only dataset, it takes numerous clicks to go into each commercials and Project area and validate for no real good reason. It would save a bit of time to have a Validate all butto...
Guest
over 8 years ago
in Validate Data
0
Idea Accepted - Gauging Support
For the 50 200 migration tool to migrate the Ex Ref field
Currently when you migrate from Sage 50 to Sage 200, the reference and details field are migrated on the PL/SL transactions. However the ex ref value isn't migrated. It is lost in the ether. Can the migration tool be updated to migrate the ex ref ...
Guest
over 8 years ago
in Ex Ref / Migration Tool
0
Idea Accepted - Gauging Support
Narrative field to exist in trader ledger transaction tables
To display the narrative on reports and layouts, e.g. Purchase Remittance, requires the inclusion of the NLPostedNominalTran/NLDeferred NominalTran/NLPendNominalTran table(s) (depending on system configuration) by joining on the UniqueReferenceNum...
Guest
almost 8 years ago
in Database
0
Idea Accepted - Gauging Support
Expand SYSNominalAuditTrail table to Include SYSAccountingPeriodID
Expand SYSNominalAuditTrail table to Include SYSAccountingPeriodID as this would allow us to determine what Period a transaction was posted to which currently isn't possible in this area.
Andrew Siddles
over 8 years ago
in Database
0
Idea Accepted - Gauging Support
Improve traceability in SYSFeatureErrorLogging when deleting a bin location
When a bin location is created against a stock item, SQL SYSFeatureErrorLogging shows &Add New Location for item: ABBuiltIn/15/0/2& If you amend the name of the bin, SQL SYSFeatureErrorLogging shows &Edit Location for item: ABBuiltIn/1...
Guest
about 11 years ago
in Database
0
Idea Accepted - Gauging Support
