Jump to content

Naoki GroupeIDF Dev

Members
  • Posts

    4
  • Joined

  • Last visited

Posts posted by Naoki GroupeIDF Dev

  1. 38 minutes ago, Joshua Getner said:

    No matter what I have been getting this 500 error back.  As stated previously this worked with no issue before.  If I am unable to get this resolved.  We will need our clients to use different software for accounting.  This is urgently needing fixed.  

    [{"$severity":"error","$dataCode":"UnexpectedError","$message":"An unexpected error occurred.","$source":""}]

    I've never managed to replicate this issue on fresh test accounts, even with the same ledger account data. I have only been able to replicate this on the production account.

    I agree with the urgency of the situation: with all due respect, an accounting software that doesn't have a working invoicing solution is simply unusable. Please escalate this bug.

  2. 2 hours ago, Steel, Mark said:

    Thank you all for your input.

    We've located examples in our logs and are currently investigating the cause.

    We'll let you know as soon as we discover the cause.

    Thanks

    Mark

    I have not been able to replicate on my end in my test environment, so it might be related to settings or something else.

    Please keep us updated on the issue!

     

    Thanks!

    P.S. Are there any news about developer trial versions for Sage? Making multiple email aliases and getting all data reset every 30 days is very counter-productive.

  3. Hey there,

    Can confirm this is an issue for me as well. It was working in production on the the 26th of April, and this error has been popping up since the 27th. I have a CA_NO_TAX tax_rate_id with a specified tax_amount of 0  (due to a breaking change that was randomly pushed at the end of march that forced this tax rate to specify a tax amount of 0). This issue is occurring with all sales_invoices that I try to create for multiple different customers, to no avail.

    Wierdly enough, trying the exact same request in my test environment, and therefore with different ledger accounts and contacts, is successful.

    I am therefore assuming this is related to ledger accounts and not contacts.

    I will investigate further to see if I can somehow replicate the issue in my test environment.

×
×
  • Create New...