Done! Thank you!

It appears that I can hit sys_properties table with REST. This works, but I haven’t yet discovered the security ramifications. These properties were created within the same application scope so maybe that has something to do with success so far:

$scope.query = ‘?sysparm_query=name%3Dx_kasc_ev_charging.session.length&sysparm_fields=name%2Cvalue’;
$scope.url = ‘/api/now/table/sys_properties’ + $scope.query;

//CALL TO REST SERVICES (angular)
//———————
$http({
method:’GET’,
url:$scope.url,
transformResponse: undefined}).then(function(response) {
console.log(response.data);
$scope.data = angular.fromJson(response.data);
console.log($scope.data[‘result’][0].name);
}).catch(function(response) {
console.error(‘Error’, response.status, response.data);
})
.finally(function() {
console.log(“All Done”);
});
//———————

CONSOLE OUTPUT:

{“result”:[{“name”:”x_kasc_ev_charging.session.length”,”value”:”2″}]}
x_kasc_ev_charging.session.length
All Done

Hey David, It doesn’t surprise me that scoped apps have made this more difficult. I’m not sure off the top of my head what an alternative solution would be but if I think if anything I’ll let you know.

Nice catch! I’ve corrected the code above.

Complete script would be:
var rec = new GlideRecord(‘sys_properties’);
rec.addQuery(‘name’, ‘your.property.name.here’);
rec.query();
if(rec.next()){
var yourPropertyValue = rec.value;
}

or:
var rec = new GlideRecord(‘sys_properties’);
rec.addQuery(‘name’, ‘your.property.name.here’);
rec.query();
if(rec.next()) var yourPropertyValue = rec.value;

You’re correct. the ‘get’ method only works client-side if get based on the sys_id of the record. To query using name (or any other attribute) from the client, you need to use the full GlideRecord query syntax. I’ve updated the client script section above to reflect this change.

It seems that doing:

var rec = new GlideRecord(‘sys_properties’);

rec.get(‘name’, ‘your.property.name.here’);

in a Client Script does not work anymore… :-(

Alain