When running the following Ad-Hoc Query in a Network Instance, the results show that a specific field is blank even though that field is populated before the report is run. The database is also refreshed. In this case, it is evident that this specific field was populated months ago (January 25th, as noted in the Revision History), and the last Database Refresh completed an hour ago. Why is the field not showing as populated in the report results. See the screenshot below:
select vid__v, corporate_name__v, alternate_name_1__v, alternate_name_2__v from hco where vid__v = 654630041270123456(sample)
This behavior is expected. The cause of this inconsistency is that the specific field in question (Alternate Name 2 in this example) has values which are added before the field is enabled in the Data Model (which in this case occurred on February 21st). Only records that are updated after this date are re-exported to the database to insert values into these fields.
Veeva Network Online Help: Creating Ad-Hoc Queries
Send us your feedback: We're always looking for advice to help improve our Knowledge Base! Please let us know if this article was helpful or provide feedback on how we can improve your experience here.