Hi Vinn, I presented a solution via configuration files but you are right the UI option is better (Centralized-Management > Data Enrichment). In above example, the CSV file gives the rules to implement the tag.  The concept is to be able to scope & identify the data you need to enrich. I assumed you needed to filter on VMDK file of your Virtual Machine, there is no particular filter for the datastore which may be needed depending or your naming convention.  As for the impact of vm motion it depends also on the mapping and naming convention. Keep in mind that property updates are not "real-time" anyway.  If you have more questions or you need webex feel free to contact me at : florian.coulombel[NAME].com  Cheers
From the perspective of a VM report, how can I double the size (UsedChargeableCapacity) of a VMDK file if the datastore it is stored on is distributed?  I am thinking of using the path to the VMDK file.  My naming convention for distributed VMFS datastores is reliable.  So if I can apply a conditional based on the name of the datastore (part) then I can use that to do an multiplication or add the UsedChargeableCapacity to itself.  How do I read the the part property and have ViPR make a decision based upon it?
VMs Stored on VPLEX Distributed Volumes