Building Automation Knowledge Base

Issue New user is unable to complete the BDP registration process Product Line EcoStruxure Building Data Platform Environment Building Data Platform Cause User clicks the registration button which has been mailed to them but get an “Opps! This page cannot be found.” error Resolution The user is already logged into BDP using another User account. This can occur if a SE user is using more than one email address to manage accounts with different business relationships. This can also occur if the user is a SE employee who is testing the system. The user should log out of BDP. Or use Incognito mode.   NOTE: If the user is logged into another SE app, this could also pose a problem. TBD

Issue New user with an external email account was created but never received an email invite Product Line EcoStruxture Building Data Platform Environment Building Data Platform Cause Incorrect email User registered for the wrong platform (UAT or Prod) IDMS issue Resolution Attempt to log in, this should kick off the registration process again Verify that the email is correct Verify which platform the user should be registered to

Issue Receive API error codes while trying to connect my API to BDP. Product Line EcoStruxture Building Data Platform Environment Building Data Platform Cause Receive the following Error codes: 400 Bad Request 401 Unauthorized 403 Forbidden 404 Not Found 500 Internal Server Error Resolution 400 Bad Request The server cannot or will not process the request due to something that is perceived to be a client error (e.g., malformed request syntax, invalid request message framing, or deceptive request routing) 401 Unauthorized Although the HTTP standard specifies "unauthorized", semantically this response means "unauthenticated". That is, the client must authenticate itself to get the requested response 403 Forbidden The client does not have access rights to the content; that is, it is unauthorized, so the server is refusing to give the requested resource. Unlike 401 Unauthorized, the client's identity is known to the server 404 Not Found The server cannot find the requested resource. In the browser, this means the URL is not recognized. In an API, this can also mean that the endpoint is valid but the resource itself does not exist. Servers may also send this response instead of 403 Forbidden to hide the existence of a resource from an unauthorized client. This response code is probably the most well known due to its frequent occurrence on the web 500 Internal Server Error The server has encountered a situation it does not know how to handle   Successful responses 200 OK The request succeeded. The result meaning of "success" depends on the HTTP method: GET: The resource has been fetched and transmitted in the message body HEAD: The representation headers are included in the response without any message body PUT or POST: The resource describing the result of the action is transmitted in the message body TRACE: The message body contains the request message as received by the server 201 Created The request succeeded, and a new resource was created as a result. This is typically the response sent after POST requests, or some PUT requests. 202 Accepted The request has been received but not yet acted upon. It is noncommittal, since there is no way in HTTP to later send an asynchronous response indicating the outcome of the request. It is intended for cases where another process or server handles the request, or for batch processing.