Showing results for 
Show  only  | Search instead for 
Did you mean: 
Engaged Sweeper
This isn't a big issue, but when I run the report "Disk: Workstations less than 1 GB free HD", it returns a report with the following fields:

tblAssets.AssetName, tsysOS.OSname, tblAssets.Description, tblDiskdrives.Caption, tblDiskdrives.Free, tblDiskdrives.Size, tblDiskdrives.Lastchanged

However, when I go into "Edit Report", the SQL does not agree with those fields, instead it says that the output fields will be:

tblAssets.AssetID, tblAssets.AssetUnique, tblAssets.Description, tblDiskdrives.Caption, tblDiskdrives.Freespace, tblDiskdrives.Size, tblDiskdrives.Lastchanged, tsysOS.Image.


The issue I am having is when writing a view, I can't use the exact SQL shown in the 'Edit Report' view because of this discrepancy. It isn't that I can't make it work, I can find the appropriate fields and modify the SQL just fine; but this seems to be a display bug at the very least. It creates a lack of confidence that the 'Report Builder' tool is truly accurate or at least truly a reflection of the underlying SQL that generates the report output.

Is this a bug?
Lansweeper Alumni
This is expected behavior. The AssetID field is automatically filtered from your report output, unless you assign an alias to the field. This field contains no useful information, only an internal reference number. The reason it is added to reports is to turn asset names into links. The AssetUnique field is also automatically converted to the asset name, unless you assign an alias to the field.