Question:

The user has noticed that upon running an Ad-Hoc Query on a profile's specific field in Veeva Network (Example Field: alternate_name_2__v), the query does not return any value for that field, even though the field is populated on the record's profile page and in its Revision History. Why does this occur?  

Answer:

The cause of this inconsistency is that the values for the alternate_name_2__v field were loaded on an earlier date (for example 2015 January), compared to when the Data Model fields for alternate_name_2__v were enabled (for example, 2015 February). Only records which are updated after that date are re-exported to the data warehouse to insert values into these fields.

To resolve this, the user should proceed with requesting a full warehouse reload from Veeva Support. Once the warehouse reload is completed, values for the field alternate_name_2__v are visible in the Reports as well as the profile for the affected entities.

Related Documentation:

Building reports with SQL queries

Thank you