Going through the data file repair process sounds like the path we were treading down as well.
If you are needing future assistance don't hesitate to get in touch.
Selecting the Committed value on an item's record loads up the Analyse Inventory [Detail] report with that item filtered. So my first question would be what happens if you run the report naturally i.e. Reports>>Inventory>>Analyse Inventory [Detial] -- Display Report. Does it work as expected or do you get the same result?
I also would be keen to know what happens in relation to the following:
If I was to take a guess at what is happening, it's likely a transaction that has not been recorded correctly or broken itself in some way, and therefore when you run that report it's failing to load due to that transaction. However, if you want to confirm the above situation we further analyse the situation.
Hi Steven, Thanks for your comprehensive reply. The Detail report does not work either, the summary report does work though. Item Register Detail seems to work. Sales(Item Detail) works. Item List Summary report is fine.
Situation is for all items.
Multiple PC's.
I may have found cause. I have a contractor implementing an API connection for importing PO's. I went to one of the test PO's & a MYOB crash occurred. I have attached a txt file of the crash info. I managed to delete the PO, and another one but still the issue exists.
What would you recommend. Thanks!
Thanks for confirming that information. The Summary report working doesn't surprise me as it will not be looking too much into the overall transactions just the amounts, whereas the Detail one does list the transactions and therefore would be more looking at the individual transactions. I'm surprised that the other reports work fine though, I would have thought they would have failed based on the same principle.
With regards to the error report, having a read it looks like the system appears to be failing with regard to the terms of the transaction.
(Unknown): ShowUIView(EnterPurchases,...,...) ---> MYOB.Huxley.API.HuxleyDataException: (DataInvalid): Data Entity Term.PaymentType is out of range. Unable to convert into TermsPaymentType
My overall recommendation would be to delete the transactions that have been sent by the API. If the crash is occurring when opening those transactions its a good indication that they are the ones that are generating this situation. I would recommend speaking to that contractor as well as I would say there is a problem with the importing of those records with the API.
If deleting those transactions is not feasible, do you have a backup prior to that API work? If so, try restoring that backup with a different name. Run the report to see if worked and then see if you can send a transaction or a small number of transactions through that API. If so, generate the report does it generate the error? If so, does deleting that transaction/small number added through the API allow it to be run?
Hi Steven,
Thanks for your reply. There are two transactions (Purchase Orders). I have tried to delete them & MYOB crashes. Restoring a backup is possible however It's a real challenge due to the volume of transactions that will need re-entry. I have sent the file to DFR Team to review & hopefully we can organise a repair on our live file with minimal downtime.
I have stopped the contractor at this stage to allow us to find a "safe" method to progress with this API integration development. eg. Don't use our live file! :-)
If you recommend a different approach to this, please advise.
Thanks for your help. Regards Martin
Going through the data file repair process sounds like the path we were treading down as well.
If you are needing future assistance don't hesitate to get in touch.
