Reply To: HVR Burst Table

Simon Faas


When a column is marked as absent using ColumnProperties /Absent it will still be created in the burst-table. The reason is that this column may be used in an /IntegrateExpression to calculate a value for other columns.

To get rid of these columns completely you can delete them from the channel  (double click on the table, find the columns, and delete them; alternatively you can delete them directly from the HVR catalogs hvr_column table in the hub repository)

After this run HVR Initialize for the Capture and Integrate location with “Scripts and Jobs” checked as well as “Table Enrollment”

After this an Online Refresh with re-create mismatched tables option for the affected table will be necessary to get the data and layout back in sync

Test drive
Contact us