Posting issues to BIM 360 returns 500 error

[steve.alberts]

Hi everybody!

I have been trying to post issues to BIM 360 via the API, using Postman. However, so far I have not come any further than receiving a 500 error. I have tried to post the example that's been given on 

https://forge.autodesk.com/en/docs/bim360/v1/reference/http/field-issues-POST/

but even that one gives a 500 error. Even if I stick to just the mandatory fields that are listed on the instructions, I still get a 500 error. 

{
    "data": {
      "type": "quality_issues",
      "attributes": {
      "title": "Postman Issue",
      "ng_issue_subtype_id": "1a88b8e4-7032-4515-ad0a-9a7196bb88ed",
      "ng_issue_type_id": "51126ba8-9f3f-4099-acc9-82b4e102b7ce"
      }
    }
}

More worryingly, if I remove any of these attributes, it still lists as 500 and doesn't give me any meaningful validation error. So it seems the attributes I am passing into the API aren't being validated as I'd expect them to be. 

Does anyone know how to resolve this? Or does anyone have an example request for posting issues that does actually work? Thanks in advance!

[steve.alberts]

Hi everybody!

I have been trying to post issues to BIM 360 via the API, using Postman. However, so far I have not come any further than receiving a 500 error. I have tried to post the example that's been given on 

https://forge.autodesk.com/en/docs/bim360/v1/reference/http/field-issues-POST/

but even that one gives a 500 error. Even if I stick to just the mandatory fields that are listed on the instructions, I still get a 500 error. 

{
    "data": {
      "type": "quality_issues",
      "attributes": {
      "title": "Postman Issue",
      "ng_issue_subtype_id": "1a88b8e4-7032-4515-ad0a-9a7196bb88ed",
      "ng_issue_type_id": "51126ba8-9f3f-4099-acc9-82b4e102b7ce"
      }
    }
}

More worryingly, if I remove any of these attributes, it still lists as 500 and doesn't give me any meaningful validation error. So it seems the attributes I am passing into the API aren't being validated as I'd expect them to be. 

Does anyone know how to resolve this? Or does anyone have an example request for posting issues that does actually work? Thanks in advance!

[mikako_harada · Accepted solution]

I just tried at my side. It is working. While trying to test, I also notice that if I put a wrong containerId, I get 500 error.  

Could you double-check if you have a valid container id?  You can follow the instruction here: 
https://forge.autodesk.com/en/docs/bim360/v1/tutorials/issues/retrieve-container-id/

(side note: container ids will be eventually the same as project id.  But not all module has done this and older project has separate container id. So you will still need to get it data management call. new ACC unified projects should be using project id.)    

[mikako_harada · Accepted solution]

I just tried at my side. It is working. While trying to test, I also notice that if I put a wrong containerId, I get 500 error.  

Could you double-check if you have a valid container id?  You can follow the instruction here: 
https://forge.autodesk.com/en/docs/bim360/v1/tutorials/issues/retrieve-container-id/

(side note: container ids will be eventually the same as project id.  But not all module has done this and older project has separate container id. So you will still need to get it data management call. new ACC unified projects should be using project id.)    

[steve.alberts]

Container id is what turned out to be the issue!

[steve.alberts]

Container id is what turned out to be the issue!

[OpeningsStudioBIM360Export]

UPDATE: my issue was the json format, forge is very ambiguous with multiple json data structures containing the same names (e.g. "data", "attributes", etc). I am now getting "201 - Created" with a complete response. HOWEVER, when I go directly into the project, I cannot find any new issues in the issues list??? I don't understand, any suggestions?

Hi @mikako_harada,

This is not working for me either, and I have confirmed that my issue container ID (from the retrieve container ID call) is exactly the same as the project id. As the last person said, the message is not very useful:

"Server returned HTTP response code: 500 for URL: https://developer.api.autodesk.com/issues/v1/containers/bd8dc408-5e5c-4611-969a-815d7233fd0d/quality...

I have all the required fields covered. Any other suggestions?

Thanks,

David

[OpeningsStudioBIM360Export]

UPDATE: my issue was the json format, forge is very ambiguous with multiple json data structures containing the same names (e.g. "data", "attributes", etc). I am now getting "201 - Created" with a complete response. HOWEVER, when I go directly into the project, I cannot find any new issues in the issues list??? I don't understand, any suggestions?

Hi @mikako_harada,

This is not working for me either, and I have confirmed that my issue container ID (from the retrieve container ID call) is exactly the same as the project id. As the last person said, the message is not very useful:

"Server returned HTTP response code: 500 for URL: https://developer.api.autodesk.com/issues/v1/containers/bd8dc408-5e5c-4611-969a-815d7233fd0d/quality...

I have all the required fields covered. Any other suggestions?

Thanks,

David