- This topic has 1 reply, 2 voices, and was last updated 6 years ago by .
-
Posts
-
This might be a stupid question, but every time I add a bps file to an instance the columns I use in the regular view are totally different compared to when I add it to the service.
It seems columns are bound to the BatchPatch instance and service instance and not to the files themselves? How can I schedule a report with the columns I want to see instead of the ones that are configured now?
goal: Set up an automatic monthly report that does a Windows Update check of all hosts and sends it via mail afterwards.
Thank you for highlighting this. I have looked into this, and I believe we have two bugs here plus one ‘feature’.
1. BUG – Email notifications sent for any grid, regardless of whether that grid is running in the service instance or regular instance, will include a HTML representation of the grid, but this HTML grid does not obey the column display ordering that is set in the main BP grid.
2. BUG – When a grid is loaded into the service instance and then is displayed in the service instance viewer, column display ordering that is set in the main/regular BP instance is not obeyed in the service instance viewer.
3. NOT A BUG – When a grid is running in the service instance and loaded into the service instance viewer, or when a grid is running in the service instance and emailed as HTML via a scheduled task, the resultant output includes the previously hidden columns in addition to all the visible columns.
We will look at fixing 1 and 2 in a future build. We will consider updating the functionality for 3 so that hidden columns are no longer displayed in the service instance viewer nor in the HTML email reports that are sent from the service instance.
- You must be logged in to reply to this topic.