Skip to Main Content
Sage 200 UKI Ideas Portal

Please note the following Sage 200 Ideas Portal Guidelines apply to the use of this portal.

ADD A NEW IDEA

Clear

Ideas

Showing 13

SQL Triggers

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
Andrew Siddles over 1 year ago in Database 2 Will not implement

The Nominal Transaction table must have VAT Code/VAT Period ID fields against each NL Posting

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...
Rustum Khedkar over 1 year ago in Database 0 Idea Accepted - Gauging Support

To be able to import multiple contacts on PL/SL accounts

On importing Customer or Supplier accounts, you can only import one contact per account, despite being able to input multiple manually. It would be good to be able to import them on the Customer/Supplier Account import or a separate import
Gary Butler almost 7 years ago in Customer/Supplier Account 0 Idea Accepted - Gauging Support

Prevent duplication of URNs

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...
Tim Critchley over 1 year ago in Database 0 Idea Accepted - Gauging Support

For the Suppliers Export option to export Supplier Bank Details

I was so happy to see the new functionality to export Customer and Supplier records that I almost spat my tea out when it was announced. Great, something to save time on creating new datasets with the same customers and or suppliers. Sadly the exp...
Gary Butler over 6 years ago in Customer/Supplier Account 0 Idea Accepted - Gauging Support

Include all Customer fields on the SL Import

The customer account import routine does not include all the fields on the customer record - eg: DUNS Number is missing. Update the importer routine to include all SLCustomer fields
Alistair Burnett over 1 year ago in Customer/Supplier Account 0 Idea Accepted - Gauging Support

User correct DateTimeCreated in the database!!!

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...
Guest over 8 years ago in Database 1 Idea Accepted - Gauging Support

Flag imported items in the SQL Database

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...
Guest over 10 years ago in Database 0 Idea Accepted - Gauging Support

Remove the forced default NL code on Customer and Supplier import

This has been introduced since you changed the import/update feature in Sage 200. Previously all customers and suppliers could be imported without a NL code. Now they cannot. Its forcing me to run scripts on every db to remove a default NL code. A...
Guest over 6 years ago in Customer/Supplier Account 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 over 7 years ago in Database 0 Idea Accepted - Gauging Support