You are looking in the wrong place in the object model.  VMWare Virtual Machine is an extension of the Host object model.  Think of the Host as the base model from the car dealer, and the VM as the base model with all of the bells and whistles added to make it into a street racer.  If you enter a VM name in the upper search bar, you will see that the results returned include objects of different types, probably a VMWare Virtual Machine, and a Host.  Selecting the VMWare Virtual Machine will take you to the screens specific to the VMWare object models.  Similar results for HyperV, etc.  There is still a Host record for each VM, just as each car from the factory has the base model in there somewhere.  It just won't have all of the bells and whistles.  Looking at your attachment, I'm thinking what you are seeing on the dashboard might be what you see in Virtual Center.  VMs have a name which shows up on the list in Virtual Center, which can be separate from the actual name assigned to the VM inside of the Operating System.  If you correct the naming in VC, I think you will find that the correction will automatically flow through to vFoglight.
Please see attached file.  All hosts based on the same templates show up under the same name in Hosts. Is it possible to configure vFoglight to fetch the vCenter naming for the hosts instead of using the VMware disk file name for the actuals hosts?
Hosts naming - how to use VMware name instead of file name