Database

I know it is not allowed to be able to use SQL Triggers on the Sage 200 databases but I believe this should be considered

When it comes to reconciling VAT Transactions for a submission period Vs Nominal posted transactions, there is no direct link between the two. It will be useful to have each transaction's VAT Code, VAT Type, VAT Period ID stored in Nominal Transac...

On very rare occasions you may see duplicate URNs posted to the Sales Ledger due to environmental issues (deadlocks etc), this could possibly be prevented by setting a constraint on the SLPostedCustomerTran URN field field in the database to preve...

This will assist support on the product, I needed to on several occasions try to find how data has got into the system when a customer is sure the data was not imported. It would be great if when a item is imported into sage via one of the standar...

We create a number of reports in Sage based on data directly from SQL. We use the DateTimeCreated field in a number of tables to provide KPIs and time triggered reports. DateTimeCreated has always been generated from the Server time that SQL is ru...

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...

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.

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...