SellerDeck Link for Sage 50 Release Notes
Contents
1. ssscccccecsssssssnsseeeecessesnsaeceeeesssssseeeeeees 14 1 32 Summary of changes in release DEWA csscccccccessssesssceeeecsssessaeeeeeesseesstseeeeess 14 1 33 Summary of changes in release DBVA ccssccccccesssssssceecscessesnsaeceeeeeseesaeeeaeens 15 1 34 Summary of changes in release DAIA cccessccccecesssssnseeceescessesaaeeeeeessessaeeaaeees 15 2 AMRFOCUCTIONS a isescsccedesncseasdce cds es wicbdvaddvecdvaccdeccvasesd ucseacvcuesediss s sescdevasveced cbsibesessvadiesviss 16 3 4 Dils DESCHIPUIOMN seer eci6 sects E and Sis eeie es hess T E E ES 2 2 Certified Compatibility 0 cscs coders hiccecees cose casa ateds sh iea e i aean aaa T a iieiaei 2 3 Current limitations of the SellerDeck Link SOftWAFre ee eet eeeseeeeeeeeeeeeeteeteaaeetenes 2 3 1 OLE Message on Installation ccccccccccscssssssseececececesssneaeeeeecesseseaaeeeeeeseesseesees 2 3 2 SellerDeck Business Plus Multi USP o oo eee ceccceceeeeeeeeeeeeaeeeeaceceeeeeeeaeeeeaeeeteeees 2 3 3 SellerDeck Enterprise Microsoft SQL Database cccsccccccecesssssseeeeeeeseesssaees Release Version Getails ci i ccvsssikescesseesssncsetsesvsesesconcdetes sessescssncediveevsasecdascdaaescnsssesesees 3 1 Installation directory StrUCtULe in aeee aeaa a aRar EE OEE ATAARE nE AE 2 2 Fil VErSiON NUMDELS iscsi a niaaa a hers aa aaa aa ea a a aa a Taa 3 2 Install program Version NUMDELS e cccccccecsssesssec2. Sage 50 2 2 Certified Compatibility SellerDeck Link is compatible with versions 2011 2012 2013 amp 2014 of Sage 50 Accounts It will work with the Accountant Accountant Plus and Financial Controller versions of Sage 50 Accounts Accounts Plus and Accounts Professional versions of Sage Accounts 50 SellerDeck Link is also compatible with software versions 10 x Business Designer and Enterprise 11 x Business Designer and Enterprise SellerDeck 2013 Business Designer and Enterprise SellerDeck 2014 Business Designer and Enterprise This release is NOT compatible with the following versions 4 0 7 and higher 4 0 X Business 4 1 x Business 5 x Business and Developer 6 x Business and Developer 7 x Business and Developer 8 x Business Designer and Enterprise 9 x Business and Designer Please note that because version 9 and below are not supported by this release of SellerDeck Link you must also upgrade to a newer version of SellerDeck Ecommerce Business or above 2 3 Current limitations of the SellerDeck Link software 2 3 1 OLE Message on Installation Occasionally the following message may be displayed during installation of SellerDeck Link Reboot required The OLE system files are in use and cannot be updated The installation must restart Windows to update OLE before it can continue Press Yes to restart Windows and continue the installation or press No to
3. created for a v6 licensed Business site 1 27 Summary of changes in release 2 1 Description Support for Sage Line 50 v11 was implemented Link continues to support the use of license keys from previous Link for Sage versions as well as license keys for v7 Business and v7 Developer Payment details are now transferred into Sage Line 50 Some report fields were not correctly set in Sage for transferred invoices and sales orders These were SOP_ITEM TAX_RATE and INVOICE_ITEM TAX_RATE This did not affect tax amounts on orders but the display of the tax rate could be displayed incorrectly Sometimes depending on whether the Include salutation checkbox is checked or not in Link the assigned customer in an invoice in Sage would be the default customer in the Link Transaction types tab Description Simultaneous editing of SellerDeck to Sage and Sage to SellerDeck is now not possible Better diagnostic error reporting has been implemented when Customers in Sage have incomplete data for successful transfer to SellerDeck Desktop Sage Line 50 now includes Products and Invoices in v9 Accountant and later Link now enables this functionality The web site description rather than the payment method in Business settings Payment and security was put into the dropdown in Link for transaction type for PSPs 1 28 Summary of changes in release EGXA Support
4. exit the installation If this happens then do the following e Press the No button and reboot the computer Then double click the setup EXE file again to restart the installation e This should cause the SellerDeck Link installation to complete successfully If not then please contact SellerDeck Support directly 2 3 2 SellerDeck Business Plus Multi User If you are looking to use SellerDeck Link with the Multi User version of SellerDeck Business Plus then SellerDeck Link must be installed on the same computer that has SellerDeck Business Plus installed on it and also has the shared multi user database installed on it 2 3 3 SellerDeck Enterprise Microsoft SQL Database SellerDeck Link will throw a Server rejected the connection Access to selected database has been denied warning when SellerDeck Enterprise is switched between Access and SQL Sites See Appendix E in the main help for more information 3 Release version details 3 1 Installation directory structure The directory structure created when the SellerDeck Link software is installed is SellerDeck Link Sage 50 ActToSage exe is the SellerDeck to Sage 50 application SageToAct exe is the Sage 50 to SellerDeck application System files for the interface SellerDeck Link Sage 50 docs The help text is SellerDeck Link for Sage Help chm SellerDeck Link Sage 50 Datafiles Site1 This is the default site set in the user interface 2 2 File version num
5. for Business and Developer v7 was added Performance when transferring orders into Sage over a network has been greatly improved The license key for Link for Sage is now either a v7 Business or a v7 Developer license key 1 29 Summary of changes in release DMQA Description Orders are now transferred into Sage in order sequence In other words if orders 01 and 02 within SellerDeck Desktop are transferred to Sage in a single export and the Get next available Invoice Order number from Sage feature is used then 01 will use the lower Sage number etc Customer Contact Details from is a new profile option in SellerDeck to Sage See the getting started guide for details Site names can be now appended to the application path without using the ui parameter The product reference translation feature of Sage to SellerDeck when Do not translate sage reference with error message and error log is selected now only transfers those products which are in the table Include Contact Name in Company Addresses is a new profile option in SellerDeck to Sage Put SellerDeck Order Number in Customer Order No is a new feature in SellerDeck to Sage and enables a checkbox selection of this option DAO 3 5 is no longer presented as an installation option on Windows XP 1 30 Summary of changes in release DIZA Description Support for Sage Line 50 Version 10 is implem
6. 10 1 18 Summary of changes in release 2 4 0 ccccsessccececesessesseeceeeceesesneaeceeeeeseessaeauaeees 10 1 19 Summary of changes in release 2 3 3 ccccccssssscececesessesseeeececessesnaaeeeeeeeseesaeauaeess 10 1 20 Summary of changes in release 2 3 2 cccecssssececececeesesseeceescessesnsaeeeeeeeseesaaeauaeens 10 1 21 Summary of changes in release 2 3 1 cccccssssscececesessenseeceescessessaaeeeeeeessesaeauaeees 11 1 22 Summary of changes in release 2 3 0 cccssssscccecsssesesseeceeecessesnsaeeeeeeeseesaeauaeess 11 1 23 Summary of changes in release 2 2 0 ccccsessccececeseesssseeceeecessesnnaeceesesseeseaeauaeens 11 1 24 Summary of changes in release 2 1 4 cccccssssscccecessesesseeeececessesneaeeeeeessessaeauaeess 11 1 25 Summary of changes in release 2 1 3 cccccssssscececeesssesseeceescesseseaeeeeeesseeseaeauaeess 11 1 26 Summary of changes in release 2 1 2 cccccssssscececessesesseeceeecessesneaeeeeeessssseaeauaeess 12 1 27 Summary of changes in release 2 1 ceccseessssecececessesesececeeseseseuaeeeeeeesessaeaaaeess 12 1 28 Summary of changes in release EGXA cccessccccccessssesseceeeecessesneaeeeeeesssesaeeeaeens 13 1 29 Summary of changes in release DMOA scssccccccsssssessseeeecessessaeeeeeeeseessneeeeeess 13 1 30 Summary of changes in release DIZA cccsesssccceceesssssseeceeecessesenaeeeeeesseessaseaaeess 14 1 31 Summary of changes in release DGAA
7. SellerDeck Link for Sage 50 Release Notes SellerDeck Ltd Date 12 November 2015 Release 2 8 3 Revision History ila sali 3 Sept 2001 Karoly Neh z Release 0 1 Beta 1 0 1 Oct 2001 Kevin Wilson Release 1 0 BKJA 1 1 19 Dec 2001 Kevin Wilson Release 1 1 BNOA 1 2 19 April 2002 Kevin Wilson Release 1 1 1 CECA 1 3 31 May 2002 Kevin Wilson Release 1 1 2 CFUA 1 4 30 July 2002 Kevin Wilson Release 1 1 3 CGZA 1 5 30 Sept 2002 Kevin Wilson Release 1 2 CIKA 1 6 16 Oct 2002 Kevin Wilson Release 1 2 CLBA 1 7 17 December 2002 Kevin Wilson Release 2 0 CNMA 1 8 13 January 2003 Kevin Wilson Release 2 0 DAIA 1 9 26 February 2003 Kevin Wilson Release 2 0 DBVA 2 0 8 May 2003 Kevin Wilson Release 2 0 DEWA 2 1 12 June 2003 Kevin Wilson Release 2 0 DGAA 2 2 27 August 2003 Kevin Wilson Release 2 0 DIZA 2 3 25 Nov 2003 Kevin Wilson Release 2 0 DMQA 2 4 29 June 2004 Kevin Wilson Release 2 1 EGXA 2 5 1 Sept 2004 Kevin Wilson Release 2 1 EJEA 2 6 8 Dec 2004 Kevin Wilson Release 2 1 2 ENDA 2 7 24 Jan 2005 Chris Dicken Note about Business Multi User added 2 8 10 May 2005 Chris Dicken Release 2 1 3 FEOA 2 9 13 June 2005 Chris Dicken Release 2 1 4 FGBA 3 0 20 Sep 2005 Chris Dicken Release 2 2 0 FKBA 3 1 1 June 2006 Chris Dicken Release 2 3 0 GGQA 3 2 21 September 2006 Darren Langley Release 2 3 1 GKDA 3 3 9th March 2007 Darren L
8. anges in release 2 1 3 Description The order number field in the persons csv export file is now handled by Link Stack Overflow message no longer received if a Sage product reference has over 20 characters and Link tries to transfer it into SellerDeck Desktop The Default Customer drop down in the Transaction Types tab is now sorted in customer reference order Merchants can now assign a payment reference to appear upon the sales receipts in Sage Payment methods that are not enabled online in SellerDeck Desktop are now enabled in Link This is so any order taken offline with a different payment method will be transferred correctly Duplicate entries no longer appear in some of the drop downs in Link 1 26 Summary of changes in release 2 1 2 Description Support for creating Sales receipts in Sage from payments entered into SellerDeck Desktop Overflow error sometimes occurred when an order was transferred into Sage which had 1 or more components where the main product cost is zero An error occurred in Release EJEA when attempting to transfer customers from Sage using Sage v6 A better user message is provided when the order csv files have become corrupted e g by editing them in excel or wrongly exporting in TAB separated format Sometimes there was a missing nominal code on S1 S2 records when created for SellerDeck orderlines which are components A Link profile couldn t be
9. angley Release 2 3 2 HCSA 3 4 4 December 2007 Darren Langley Release 2 3 3 HMZA 3 5 215 February 2008 Darren Langley Release 2 4 0 ICLA 3 6 22 September 2008 Darren Langley Release 2 4 1 IKBA 3 7 26 April 2010 Darren Langley Release 2 5 0 KEIA 3 8 26t May 2010 Darren Langley Release 2 5 1 KFAA 3 9 224 September 2010 Darren Langley Release 2 6 0 KKCA 4 0 25 October 2011 Darren Langley Release 2 7 0 LLHA 4 1 29 November 2011 Darren Langley Release 2 7 1 LMUA 4 2 5th January 2012 Darren Langley Release 2 7 2 LNQA 4 3 9t January 2012 Darren Langley Release 2 7 3 MAFA 4 4 16 July 2012 Darren Langley Release 2 7 4 MHBA 45 19th November 2012 Darren Langley Release 2 7 5 MLYB 4 6 25th January 2013 Darren Langley Release 2 7 6 NAWA 4 7 26th March 2013 Darren Langley Release 2 7 7 NDFA 4 8 13 September 2013 Darren Langley Release 2 7 8 NJUA 4 9 8t May 2014 Darren Langley Release 2 7 9 OEXD 5 0 19th September 2014 Chris Law Release 2 8 0 OJEB 5 1 13 November 2014 Chris Law Release 2 8 1 5 2 4 November 2015 Bruce Townsend Release 2 8 3 Contents 1 lt Change History een EN E NS AEN T EENES EAEE 7 1 1 Summary of changes in release 2 8 3 ccccssssccecesessessnececeessessaeeeceeseessesneaeeseeeesenses 7 1 2 Summary of changes in release 2 8 1 cccessssccccecsssesseececeessesseaeseceeseesseseeaeeseeeeeensees 7 1 3 Summary of changes in release 2 8 0 orrela rai EA EL R A E A E 7 1 4 Summary of changes in release 2 7 9 cccccss
10. bers The SellerDeck gt Sage 50 application ActToSage exe The Sage 50 gt SellerDeck application SageToAct exe 3 2 Install program version numbers SageLinkInstaller EXE This installs SellerDeck Link system files 4 Instructions for use 4 1 Introduction Navigate to Start Programs SellerDeck Link for Sage 50 in Windows You will see that there are 4 entries which can be selected e SellerDeck to Sage 50 this starts the SellerDeck to Sage 50 application e Sage 50 to SellerDeck this starts the Sage 50 to SellerDeck application e SellerDeck Link for Sage Help this opens the help text e Uninstall this uninstalls SellerDeck Link for Sage 50 4 2 The Getting Started Manual The user manual explains how to configure and use the Link software This is can be viewed at Start Programs SellerDeck Link for Sage 50 SellerDeck Link for Sage Help
11. certain circumstances Overflow error no longer occurs when exporting many Special Customer prices Option now available to set Invoice Sales Order date as the date of the order shipped in SellerDeck Desktop It is now possible to export orders with commas in their journal field with causing an error Error log file size now increased 1 21 Summary of changes in release 2 3 1 Description Compatibility with Sage Line 50 2007 1 22 Summary of changes in release 2 3 0 Compatible with v8 Country codes can now be used as part of the customer account naming scheme A global dept code of Use Fixed Value is now transferred into Sage correctly If an invoice country code of an order is blank the software now uses the delivery country code When Telephone 1 and Telephone 2 are both filled in Sage Link will now ignore Telephone 1 T9 is now used as a TAX_CODE value in the SA records created by Link 1 23 Summary of changes in release 2 2 0 Description Compatibility with v12 of Sage Line 50 Stock monitoring can now be turned off for Sage non stock items Sage versions can now be selected via a drop down list rather than radio buttons in the profile Various fixes and clarifications to the help file 1 24 Summary of changes in release 2 1 4 Description The Payment Reference field is now visible in the help screenshot 1 25 Summary of ch
12. d choices was transferred Sometimes the payment method for a created Invoice Sales order in Sage was missing This happened if the store was previously v4 and then upgraded A file produced using BATCHINVCSV would sometimes not import into successfully into Sage An Overflow error was sometimes reported attempting to transfer an order from SellerDeck into Sage This occurred when there were more than 35535 Customers in Sage Sometimes when creating a customer in Sage from the order in EC the country code was wrongly populated in Sage The country name and code for a created Invoice Sales order in Sage were wrongly set to Abu Dhabi DH This occurred with v9 of Sage Line 50 Quotes in a customers address caused a subscript out of range error to be displayed The Department No and Nominal code for components was not correctly transferred into the Invoice Sales order in Sage When no taxes were set up in SellerDeck Desktop Link required a row of blank tax entries in the tax grid to correctly transfer orders 2 Introduction 2 1 Description The SellerDeck Link for Sage 50 Accounts facilitates the transfer of data between SellerDeck Business Designer and Sage 50 Accounts Software Account and product information can be transferred from Sage 50 Accounts into SellerDeck Orders from SellerDeck can be exported into Sage 50 Accounts Note that Sage 50 Accounts was formerly referred to as
13. ecececessaeseeeescessessaeseeeeesenseesaes Instructions for USC i552 5cescckcosasssessatecsnconandonveassesadecssdcnvassescedsndedcwmededsscdadesscav es sessessase s 4T TARROGDUCUI ON Ses anan act once i a ands eb e e at aiaa 4 2 The Getting Started Manual c cccccccccssssssscecececesseseeseccssessesnsaeseeeesseesesseaeseeeesens 1 Change History 1 1 Summary of changes in release 2 8 3 Description Compatibility with SellerDeck 2016 AL 1011 Compatibility with Sage 2016 AL 1017 Export no longer fails with more than 3 Advanced Taxes AL 652 Fixed an issue that could cause wrong rounding of the VAT rate AL 1015 1 2 Summary of changes in release 2 8 1 Description Compatibility with Sage 2015 AL 993 1 3 Summary of changes in release 2 8 0 Description Compatibility with Sellerdeck 2014 AL 978 1 4 Summary of changes in release 2 7 9 Description Enabled invoices in Sage to have the SellerDeck Invoice Number AL 970 Sage Not selecting a radio button causes an error AL 973 1 5 Summary of changes in release 2 7 8 Description Compatibility with Sage 2014 AL 956 1 6 Summary of changes in release 2 7 7 Description Can now transfer foreign currency payments to Sage AL 856 Link now transfers the last digits of an order number when transferring payments to an invoice AL 890 1 7 Summary of changes in release 2 7 6 Description Compatib
14. ented in this release 1 31 Summary of changes in release DGAA Description The SellerDeck to Sage product translation table now supports a many to one relationship Multiple product references can now all map to the same Sage item code A message was sometimes displayed Invalid procedure call error when using the Sage to SellerDeck application due to the Sage database getting corrupted In some cases the tax treatment on a SellerDeck associated product within an order was not correctly set within Sage when the order was transferred 1 32 Summary of changes in release DEWA Description Global codes are now populated in the footer section of invoices and sales orders for N C Tax Code and Dept The performance of Sage link over a network has been greatly improved The sage error message below was displayed when a sales order was created in sage Warning The invoice was created from a sales order Any amendments made will not affect stock levels OK Sometimes an S1 or S2 item in an Invoice Sales order had incorrect Nominal Code and Dept Adjustments with pro rata tax and simple tax in EC couldn t be transferred into Sage Order adjustment lines had no nominal code assigned when created in sage Sometimes the SellerDeck PO purchase order number wasn t being passed into Sage A problem occurred causing a repeat price schedule to be produced in SellerDeck Desktop A sta
15. ility with SellerDeck 2013 SQL version now implemented AL 903 1 8 Summary of changes in release 2 7 5 Description Compatibility with SellerDeck 2013 AL 884 Compatibility with Sage 50 Accounts 2013 AL 887 1 9 Summary of changes in release 2 7 4 Description Rebranded Link to SellerDeck Link AL 843 Discounts defined on Totals tabs of orders are now transferred AL 854 1 10 Summary of changes in release 2 7 3 Description Customer accounts are now created correctly in Sage if they share the same postcode but address details are different Previously they were being assigned to the same customer AL 833 1 11 Summary of changes in release 2 7 2 Description No longer causes an overflow message when transferring zero priced products to Sage 2012 AL 827 1 12 Summary of changes in release 2 7 1 Compatibility with v11 AL 750 Can now use a password to connect to a remote Sage 2012 installation AL 805 1 13 Summary of changes in release 2 7 0 Compatibility with Sage 50 Accounts 2012 AL 757 Link now works with Enterprise when using Microsoft SQL Server 2008 AL 755 Product s discount rate is now properly calculated from negative adjustments AL 749 1 14 Summary of changes in release 2 6 0 Description Compatibility with Sage 50 Accounts 2011 AL 700 Link now asks the user which SDO to install during installation AL 701 Transferring large numbers of disc
16. ounts no longer causes an overflow error AL 708 1 15 Summary of changes in release 2 5 1 Description Can now enter a valid licence key if existing key from a previous installation is not recognised AL 618 1 16 Summary of changes in release 2 5 0 Compatibility with Sage 50 Accounts 2010 AL 659 Compatibility with v10 AL 663 New splash screens and icons implemented AL 665 Compatibility with Enterprise when running under MS SQL Server AL 666 Can now post a payment with a value of 0 00 AL 670 1 17 Summary of changes in release 2 4 1 Description Compatibility with Sage 50 Accounts 2009 AL 646 1 18 Summary of changes in release 2 4 0 Description Compatibility with v9 and tax inclusive pricing AL 506 Allow import of cost price from Sage to v9 AL 581 Profile setup no longer fails if payment name is too long AL 453 Manual updated to show rounding with price lists not supported AL 560 About button added to interface AL 490 1 19 Summary of changes in release 2 3 3 Description Compatibility with Sage 2008 AL 503 Batch Invoice CSV now works with Sage version 12 and above AL 382 1 20 Summary of changes in release 2 3 2 Description Compatibility with Windows Vista Creating an offline adjustment within an order no longer causes a Profile version error warning Link no longer crashes when creating customer accounts in Sage under
17. ssccececessessaececeeeseseaeeeceeseessesnsaeeseeeesensees 7 1 5 Summary of changes in release 2 7 8 cccssssscccececessessaeseeeeeseseeaeeeceesesssesneaeeseeeesenses 7 1 6 Summary of changes in release 2 7 7 ccccccessscccececessesssececesesesnaeeeceeseessesseaeeseeseseesees 8 1 7 Summary of changes in release 270r e e e E AE iE aias 8 1 8 Summary of changes in release 2 7 5 ccccssssscccececessesssaececcessesseaeeeceeseessesesaeeseeeeeeesees 8 1 9 Summary of changes in release 2 7 4 cccccesssccececessessceeecesesesneaeeeeeeseessesnsaeeseeeeseeses 8 1 10 Summary of changes in release 2 7 3 ccccesssssscececeesesscnsceeessessecseaeceeeesseessaeauaeeeeess 8 1 11 Summary of changes in release 2 7 2 cccceessssscececesessennsceecesessesneaeeeeeesssesssauaeeeeess 8 1 12 Summary of changes in release 2 7 1 ccccesssssecececeeeesscneceeeecessecneaeeeeeesseesseauaeeeeess 9 1 13 Summary of changes in release 2 7 0 cccccssssccececeesesesnsseccscessesnsaeeeeecssseseaeauaeeeeees 9 1 14 Summary of changes in release 2 6 0 cccsssscccecesessesseceecscesseseeaeeeeecssesseaeauaeeeeess 9 1 15 Summary of changes in release 2 5 1 cccecssssscececessessnneceeescessesnsaeeeecesseeseaeaeaeeeeees 9 1 16 Summary of changes in release 2 5 0 ccccssssccececeesssesseceececsesesesaeeeeecsseeseaeauaeeeeess 9 1 17 Summary of changes in release 2 4 1 cccccsessscececeesssssneceececessesneaeeeeseessesaeauaeees
18. te code greater than 2 chars couldn t be used by Link Error message transfer is failed due to profile version does not match to order files version was incorrectly reported Customer creation features should have been greyed when unlinked out because this feature is not available when unlinked Logon failed due to an unknown error was displayed when the sage installation drive had read only access over a network 1 33 Summary of changes in release DBVA Description Permission denied error message was sometimes wrongly displayed Invalid procedure call or argument OK was displayed when a customer name in SellerDeck Desktop contained both a period and a space char In v9 Sage the country is written to both the new Country dropdown and the county field Online shoppers entering periods to separate their first and surnames sometimes produced unexpected results in Sage when creating a customer record When imported into EC the delivery address lines from Sage are sometimes passed into the wrong EC Address fields 1 34 Summary of changes in release DAIA Description Link sometimes failed reporting Subscript out of range when a customer in Sage had an empty Acc Status field The Description field entry in Sage for a product is sometimes truncated when the Invoice Sales order is created in Sage This was particularly noticeable when a product which had several attributes an
Download Pdf Manuals
Related Search