Associating Attributes with a Data Standard
Function
This API is used to associate attributes with a data standard
URI
PUT /v2/{project_id}/design/standards/attribute
| 
        Parameter  | 
      
        Mandatory  | 
      
        Type  | 
      
        Description  | 
     
|---|---|---|---|
| 
        project_id  | 
      
        Yes  | 
      
        String  | 
      
        Project ID  | 
     
Request Parameters
| 
        Parameter  | 
      
        Mandatory  | 
      
        Type  | 
      
        Description  | 
     
|---|---|---|---|
| 
        ids  | 
      
        Yes  | 
      
        Array of integers  | 
      
        Attribute ID list  | 
     
| 
        stand_row_id  | 
      
        Yes  | 
      
        Long  | 
      
        ID of the associated data standard  | 
     
| 
        table_id  | 
      
        Yes  | 
      
        Long  | 
      
        Table ID  | 
     
| 
        biz_type  | 
      
        Yes  | 
      
        String  | 
      
        Table type. Four types are available: dimension table, fact table, summary table, and business table (default). Default: TABLE_MODEL Enumeration values: 
  | 
     
Response Parameters
Status code: 200
| 
        Parameter  | 
      
        Type  | 
      
        Description  | 
     
|---|---|---|
| 
        data  | 
      
        Object  | 
      
        Returned data  | 
     
Status code: 400
| 
        Parameter  | 
      
        Type  | 
      
        Description  | 
     
|---|---|---|
| 
        error_code  | 
      
        String  | 
      
        Error code, for example, DS.000 which indicates that the request was successfully processed.  | 
     
| 
        error_msg  | 
      
        String  | 
      
        Error message  | 
     
| 
        data  | 
      
        Object  | 
      
        Returned data  | 
     
Status code: 401
| 
        Parameter  | 
      
        Type  | 
      
        Description  | 
     
|---|---|---|
| 
        error_code  | 
      
        String  | 
      
        Error code, for example, DS.000 which indicates that the request was successfully processed.  | 
     
| 
        error_msg  | 
      
        String  | 
      
        Error message  | 
     
| 
        data  | 
      
        Object  | 
      
        Returned data  | 
     
Status code: 403
| 
        Parameter  | 
      
        Type  | 
      
        Description  | 
     
|---|---|---|
| 
        error_code  | 
      
        String  | 
      
        Error code, for example, DS.000 which indicates that the request was successfully processed.  | 
     
| 
        error_msg  | 
      
        String  | 
      
        Error message  | 
     
| 
        data  | 
      
        Object  | 
      
        Returned data  | 
     
Status code: 404
| 
        Parameter  | 
      
        Type  | 
      
        Description  | 
     
|---|---|---|
| 
        error_code  | 
      
        String  | 
      
        Error code, for example, DS.000 which indicates that the request was successfully processed.  | 
     
| 
        error_msg  | 
      
        String  | 
      
        Error message  | 
     
| 
        data  | 
      
        Object  | 
      
        Returned data  | 
     
Example Requests
{
  "ids" : [ "873243083737899009" ],
  "stand_row_id" : "873241295328616449",
  "table_id" : "873243083737899008",
  "biz_type" : "TABLE_MODEL"
}
 Example Responses
Status code: 200
Success
{
  "data" : {
    "value" : {
      "ids" : [ "873243083737899009" ],
      "stand_row_id" : "873241295328616449",
      "table_id" : "873243083737899008",
      "biz_type" : "TABLE_MODEL"
    }
  }
}
 Status Codes
| 
        Status Code  | 
      
        Description  | 
     
|---|---|
| 
        200  | 
      
        Success  | 
     
| 
        400  | 
      
        BadRequest  | 
     
| 
        401  | 
      
        Unauthorized  | 
     
| 
        403  | 
      
        Forbidden  | 
     
| 
        404  | 
      
        Not Found  | 
     
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.