server error 500 on field API end points.

[mnelson-disney]

https://bim360field.autodesk.com/api/get_issues

Is throwing an exception when using a valid issue_filter_id URL parameter.

Please advise. This is impacting multiple developers on our side. ( in and outside of our network)

[mikako_harada]

Hi Matthew, 

I can reproduce the error.  I will log a change request. 

In a mean time, you may workaround by using /fieldapi/issues/v1/search  with conditions parameter.  

This may help how to use conditions parameter:  

https://fieldofviewblog.wordpress.com/2015/07/16/field-api-filter-issues-by-issue-type/

Note:  I see filter_id option with issues/search. But does not look like it's functioning, either 😞  

[Anonymous]

Hi Mikako,

This is a disaster, services that we depend on for important integration work  that have been running for the last 4 years have now failed because of the bug.

Can you very urgently provide an ETA when this bug will be fixed!!!

Thanks,

Peter

[mikako_harada]

Hi Peter, 

Thank you for confirming that it was working before.  (I was wondering about that myself as I thought it was working last time ...)  

I notified the product team.  I will update you when I get new information. 

Sorry for the inconvenience.  

[mnelson-disney]

Are there any updates on this issue?

Thanks,

Matthew

[Anonymous]

Hi Matthew,

FYI, I re-wrote my application using "/fieldapi/issues/v1/search" to get around this bug.

[mikako_harada]

Hi Matthew, 

The engineering team is investigating as a priority issue.  The product manager is aware of the issue, too.   We will update you when we have more info.  

[Anonymous]

Interestingly, at the time of this post /api/get_issues is working if I send a parameter "filter_id" instead of "issue_filter_id" (i.e., keep the same code just rename "issue_filter_id" to "filter_id") .. however still fails with a 500 error if I submit the usual "issue_filter_id" parameter as specified in the API docs.

Hahaha, obviously not going to rely on this workaround long-term since this is not API-doc-consistent behavior, but still interesting.

[mnelson-disney]

Hi,

Thanks for escalating.  Any updates yet?