Unpaid Bills Report - Failed to load

[Rowling]

Tried several times to load Unpaid Bills report for one month only. Have logged out and back in, refreshed browser, eventually displays - Failed to load 

[Rowling]

Report still not working!!!!! 

[Komal_S]

Hi @Rowling 

Sorry to hear you're experiencing this. So we can investigate what's causing this problem, can you please run the report for a shorter time period and confirm if you're still getting the same error ?

[Rowling]

As noted in the original post, I was trying to run the report for one month only. Do you require it for a shorter time period than that?

[Komal_S]

Hi @Rowling 

Yes please, try it for a week or a day and let me know if it repeatedly gives the same error. 

[Rowling]

Hi @Komal_S 

It does not work even for one day. Same issue.

[Komal_S]

Hi @Rowling 

Please send me your product serial number by Private Message, and we'll run some scripts to check what the issue is.

[Rowling]

Two of the invoices you asked me to update the terms are from June and I've run this report between then and now, so why is it all of sudden not working? What do I have to change the terms to for the report to work?  What terms do I have to avoid setting in the future to avoid this issue?

[Komal_S]

Hi @Rowling 

The cause is a data problem with the TERMS on a transaction, usually when:

• Payment is Due “On a Day Of the Month”
• Discount Date “0”
• Balance Due Date “0”

This is because the Discount/Balance Due Date can't be 0 for "On a Day of the Month" type payment terms, therefore set the payment term anything other than these.  The report can entirely fail even if the offending transaction falls out of the date range selected in the report. Please change the above terms to default or something else and let me know if you still get the same problem. 

[Rowling]

I am unsure why Invoices would stop my Purchases report from running.

I did not make any changes and the report is now working. Seems like an issue with MYOB not anything on our end. Hopefully it is resolved so this does not continue to happen.