tklattribute REST call

Hello All - wondering if anyone has used the tklattribute REST implementation yet?

Here's my little quick snippet that I have tried:

<html>
   <body>
      <div id="content">Testing</div>
   </body>
   <script src="/img/dev/js/jquery-1.11.2.min.js"></script>
   <script src="/img/dev/js/common.js"></script>
   <script>
      $(document).ready(function() {
      // get ll cookie value
      var authToken = $.cookie('LLCookie');
      var url="/otcs/llisapi.dll/api/v1/tklattribute/validvalues";
      $.cookie.json = true;
              $.ajax({
                  method:"POST",
                  url:url,
      			data: {
           			id: 57538,
           			attribute_key: 2
          		},			
                  headers:{
                      "otcsticket": authToken  
                  },
                  success:function(data){
                      console.log(data);
      
                  },
                  error:function(error){
                      console.log(error);
                  }
      
              });
      });
   </script>
</html>

where;
id: 57538 is the nodeID that has a category applied. This category has a TKL attribute
attribute_key: 2 is the attrID from LLATTRDATA table for the TKL attribute of nodeID

I am getting a 500 Internal server error in the browser's console. I am using CS 16.2.6

Any thoughts or pointers?

Find more posts tagged with

Comments

HFCDev

try setting your attribute key to <catID>_<attrID>. I don't know for sure that this would work, but in other places, attr_key typically contains the category ID as well. The reason that would be is that the attr_id is only unique in the context of the category - you can have two separate attributes with ID == 2 in two different categories.
-Hugh

HFCDev

I just tried this in Postman. As I suspected, attribute_key needs to be a underscore separated list of categoryID_attrID. You can attach both parameters (ID, attribute_key) as regular parameters in a form object (i.e. multipart/form-data or ****-form-urlencoded) as opposed to a JSON object. In Content Server, the CS CGI executable still cannot process application/json even if the REST API responds with such data.
Happy coding!
-Hugh

Amardeep Arora

Hi Hugh - thanks for your suggestion in regards to prefixing the catid - makes sense. In regards to your other comment to not passing JSON in the request body to OTCS, I have made the changes I think should be sufficient within the ajax call. The 500 internal server error is no longer an issue, however i get a 400 bad request now and response JSON reports the following error "error: "Argument "attribute_key" is required."

the current ajax call that has produced this 400:

var url="/otcs/llisapi.dll/api/v1/tklattribute/validvalues";
var p = {id: 57538, attribute_key: "57869_2"}; $.ajax({ method:"POST", url:url, data: {body: JSON.stringify(p)}, headers:{ "otcsticket": authToken }, success:function(data){ console.log(data);
}, error:function(error){ console.log(error); }
});

I was hoping ajax would do the required encoding for the body part.

thanks for your assistance thus far... i see a lot of users requesting JSON as part of request body to be included with future release.

Hoping you can shed some further light here

Satya_Sridhar_Karri

Hi Amardeep,

I tested your html file by doing minor changes to work with my environment, its working. try and change it as below.

$.ajax({

method:"POST",

url:url,

data: {

id: 57538,

attribute_key: "57869_2"

headers:{

otcsticket: authToken

success:function(data){

console.log(data);

error:function(error){

console.log(error);

}

});

Amardeep Arora

Thanks Satya. So it appears we can after all pass JSON in the request body! Your HTML appears to be the same as my original post with 2 exceptions - one being the prefixing of catID to the attribute_key parameter as per Hugh's suggestion and also passing this parameter as a string. I could also reproduce the 500 internal server error by either removing the catID prefix or making it a non-string value.