Browse By Tags

  • TLS EOL work around?

    We are currently working to get our version of SAGE 100c Advanced 2017 (Version 5.40.2.0) upgraded to the latest and greatest with our SAGE consultant company. We have been working on it for Months but due to customization of the product it is taking…
  • TLS

    We are currently running Sage 100 2016. We have migrated to a new ERP system but still need to keep our Sage 100 system around for access to historical data and financials. I understand once October hits and TLS1.1 is no longer support the system will…
  • Making sure your software is up to date

    Sage is committed to keeping our customers secure. Making sure we reduce threats and take advantage of the latest technology. This means that from time to time we need to upgrade the underlying components of our products. To ensure you always benefit…
  • Avalara (Sage Sales Tax) Deprecation of TLS 1.0 and 1.1 for REST v2 (March 31, 2022)

    As Avalara continues to improve their security protocols, TLS 1.0 and 1.1 will be deprecated as of March 31, 2022. Please review Avalara's Announcement HERE and also Sage KB 114325 for more information.
  • Acesso MongoDB +v4.0 - SSL/TLS

    Desde a versão 4.0 do MongoDB que passou a ser necessário adicionar o parâmetro --tlsAllowInvalidCertificates ao comando de ligação ao MongoDB. Sem este parâmetro dá o seguinte erro: Failed global initialization: InvalidSSLConfiguration CryptDecodeObjectEx…
  • Sage Self Service and Mobile Payslip users: Security improvement notice for Administrators

    As from 3 June 2021, Sage Self Service administrators will see the following message when logging into the application: Mobile Payslip users do not log in as Admin users, therefore they will not see the Security Improvement message. Note: We ask…
  • Sage Self Service and Mobile Payslip users: Security improvement notice for Administrators

    As from 3 June 2021, Sage Self Service administrators will see the following message when logging into the application: Mobile Payslip users do not log in as Admin users, therefore they will not see the Security Improvement message. Note: We ask…
  • Release 5.6b is now available on the Sage Portal for Sage Classic and Sage Premier

    Release 5.6b is now available on the Sage Portal for Sage Classic and Sage Premier This is a mandatory update for all Sage Self Service, Mobile Payslips and Nigeria users. The following RSA SETA Specific Reports have been updated for the 2020 - 2021…
  • Sage 500 and impact of deprecation of TLS 1.0 and 1.1

    Transport Layer Security ( TLS ) is an encryption protocol intended to keep data secure when being transferred over a network. Microsoft has been announcing the deprecation of TLS 1.0 and 1.1 for the Office 365 service for more then two years and finally…
  • Total of Orders on Marketing Wave

    Hi everyone! I would like to display the total of all orders for a marketing wave in a field named 'Revenue' on the WaveDetailBox. I figure this needs to be done with TLS, but I am uncertain what entity to put this on - Orders or Opportunities. Since…
  • SaveChanges function

    In classic ASP pages in CRM I can call SaveChangesNoTLS to ensure that tablescripts aren't fired when the record is saved. I actually do this quite a lot. In the .NET API there is a SaveChanges method but no SaveChangeNoTLS. Is there any way around being…
  • Lead Address, lead_companyaddress and Persons addresses

    When one of our users enters a Lead and then converts it into an Opportunity, the address (lead_companyAddressX) goes to the Company and the user has to enter the (often same) address for the Person record. Can you have lead_CompanyPersonAddress and have…
  • Email Server parameters should include username and password for SSL and TLS authentication

    KB ID: 72613 Last Modified Date: 6-24-2019 states this enhancement request is already here; but I was unable to find it. It's almost 2020, Sage X3 should be able to send emails to SSL & TLS authenticated email servers with a non standard port#.