I noticed this also when I created my first custom view, but then these data properties disappeared when making my second one. I was able to clone the original view which had the previously used properties, but as this was a small subset of what custom attributes we use this is very limiting.
What I've tried:
What I'm using:
A followup to my previous reply:
I logged in as the local Admin account and was able to see these properties. I logged in as a vCenter Global Administrator and could not see the properties.. Not sure why that matters?
The local admin in vrops has access to everything in vrops
the vCenter Global Administrator has access to every thing in vcenter.
This does not mean that vCenter Global Administrator has access to everything in vrops it all depends on the level of access the vCenter Global Administrator has in vrops.
vCenter Global Administrator looks like it does not have the permissions to see vcenter custom attributes in vrops