EXO API End Point Issue with BOM - 500 Internal Server Error

[NickC]

Hi all,

Was wondering if anyone could shed some light on an issue I am having, only when calling the https://exo.api.myob.com/bom/ endpoint.

Other endpoints work for this client except BOMs.

See attached for the errors being recorded.

And also an error message below:

The Billomat_hdr table does have extra fields but there are no null values.

Thank you!

[NickC]

Just setup a test connection, stripped BOM hdr and lines to one record, removed all extra fields and updated nulls.

Same error: HTTP/1.1 500 Internal Server Error

They are on Windows Server 2008 R2

Might be a Windows thing? Just strange I can query other tables.

@Will_H  ?? Help?

[Will_H · Accepted solution]

Hi @NickC ,

Just so you know, you've posted in the public MYOB API forum, which is for the AccountRIght/Essentials API.  Theoretically, you should have access to the Exo specific board at: https://community.myob.com/t5/EXO-API/ct-p/EXOAPI

(Note, a valid Developer license is required to access that forum.  If you don't have access, let me know and I'll get the Forum team to fix your identity up).

Referring to your API Error log I see 2 styles of errors there;

Error 503, Unavailable, which is the message we were experiencing during yesterdays Exo API outage.

And:

2020-04-07 15:26:25.5413:ExceptionAttributes:9:ERROR:UNHANDLED EXCEPTION STOCK_ITEMS table has different number of SELLPRICE columns comparing to number defined in PRICE_NAMES. Column in question is SELLPRICE11
EXCEPTION: System.Exception: STOCK_ITEMS table has different number of SELLPRICE columns comparing to number defined in PRICE_NAMES. Column in question is SELLPRICE11
   at MYOB.ED.EXO.Cloud.Model.Repository.BomRepository.LoadSellPrices(Object data)
   at MYOB.ED.EXO.Cloud.Model.Repository.BomRepository.Map(Object data)

This appears to be saying that the problem is with the PRICE_NAMES table having a different number of sellprices compared to the STOCK_ITEMS table.  I've never specifically dealt with this error for.  

If you need me to review the individual database, please submit a Service Request and put the database in via FTP.  Or at least, send me via email:

1. The contents of the PRICE_NAMES table
2. The schema for the STOCK_ITEMS table.

[NickC]

@Will_H  You are a legend! Sorry needed to use your time.

I did not scroll far enough in the log to even see the sell price issue! Poor effort my end.

I added sellprices missing from price names into BOM header table and now works.

Also, sorry again for the wrong post location, I actually did not realise we had an EXO API section, it was at the bottom of my list.

Thanks again!

[Will_H]

@NickC  -

No problem, I'm ok with the post being int he wrong place.  Only I don't monitor this particular forum, and neither do the few partners that do lots of Exo API work.  So if you hadn't tagged me this would have ended up waiting until one of the general admins flagged it across to me.

So mostly, use the right forum next time, should get you faster answer. 

Hope you've got something fun lined up for the long weekend.