Posted: 9 Jun 2017 23:11 EDT Last activity: 16 Jun 2017 9:00 EDT
Optimize for Reporting not working for existing cases
I have used optimize for reporting for a property which is available in an embeded page of pyWorkPage( pyWorkPage.DeviceRegistration.Property). After running the wizard I don't see the property data from BLOB to a new column. Below are the observations
It is a very common issue. For existing details, the population starts by a batch and starts populating. So you may wait for sometimes. If still not populated, there are two ways to do it. 2nd one you may try.
1) You may use ColumnPopulation utility. You have to request for it.
2) Write an activity to open the objects with lock and save it again. The column will be populated. But if number of such object is very high then it might hang. To avoid that first obj-browse using this column is not null as a criteria and give max count as 1000. Then loop through the resultset , obj-open-by-handle and save with write now.
Optimization wizard should populate the values but if not then you can setup an agent to do the back filling of the new columns for existing record. Agent will ensure background processing as huge number of record update online might be slower and the system might hang or it might lost connection with Gateway error.
Looking at the property, it is part of some page. In that case when optimized the value would be in the index table , not in the work table. To get the index class name, you need to open the declare index rule which got created while optimizing.