Aggregate count not working

Dead Blade · ‎09-30-2020

Hello All, the aggregate count is not working as expected. Please help. The dot-walk addQuery should return a count of 100 for example, but I am getting 0 results.

		
var count = new GlideAggregate('alm_hardware');   
count.addQuery('model.u_field','1111111');
count.addAggregate('COUNT');  
count.query();

gs.log("This count is empty: "+count.getAggregate('COUNT'));
if(count.next()){

gs.log("This count is working: "  +count.getAggregate('COUNT'));
gs.log('count');
}

Results:

*** Script: This count is empty: null
*** Script: This count is working: 0
*** Script: count
*** Script: 
----------------------------------------------------------

The Second row should be a count of 100

Willem · ‎10-06-2020

To help you, you can run this code:

var usedModels = 0;
var grModel = new GlideRecord('cmdb_model');
grModel.addQuery('u_field', '1111111');
grModel.query();
while (grModel.next()) {
    var grHardware = new GlideRecord('alm_hardware');
    grHardware.addQuery('model', grModel.getUniqueValue());
    grHardware.query();
    if (grHardware.next()) {
        gs.log("The model: " + grModel.getDisplayValue() +  " is used in Hardware");
        usedModels++;
    }

}
gs.log("There are: " + grModel.getRowCount() + ' Models available with 111111');
gs.log("There are: " + usedModels + ' Models used for Hardware with 111111');

Please share the log results.

View solution in original post

Dead Blade · ‎10-06-2020

From the list view I cannot add u_field. It does not appear under the gear icon, which I find to be weird since u_field is on the layout view. We are able to dot walk to model to u_field on the layout view, but not the list view.

Willem · ‎10-06-2020

That it is not showing on the gear icon is normal behavior.

Can you filter the list with the field by dot walking, so:

Willem · ‎10-06-2020

If you want to add it to the list you have to do it via the Header menu: Configure --> List Layout

(this will add the column for all users)

Dead Blade · ‎10-06-2020

Willem · ‎10-06-2020

So there is no hardware that has a model with 11111 in u_field.

Why are you expecting any other result then 0? There can be plenty models with u_field 11111 but if that model is not used/set as value on Hardware, it will return 0 results. And that is correct as you validated.