We have noticed a bug in the new 2.8 (new release candidate) server where fields that were turned into "Category" format for grouping do not appear in "Category" type any more when the report is run through the 2.8 server.
This makes the correctly grouped table in 2.7 to display incorrectly after being saved down through the server.
Can you advise if this can be rectified in later versions of 2.8?
Yes screen share is good today any time outside 1530-1700, but wondering if the below descriptions suffice?
The issue flagged is that in 2.7, when a field is changed to "Category" format (which is not available to do in 2.7 within Data Manager tab), when the report is ran on our 2.8 server, the format change is forgotten. Meaning tables that are grouped by these fields are no longer grouped properly.
I can change the format of the fields to "Category" where necessary within Data Manager in 2.8, this potentially rectifies the bug, but that will mean I need to go into all my reports and do the same for all fields needed to be in "Category" format, which is ultra time consuming, especially fields that are created in the Field Manager by pressing Ctrl+F, for these I will be having to delete them all and recreate them within Data Manager.
In 2.8 we added the ability to select a field as "category" in DataManager. This was necessary to allow automatic creation of reports. I think it would be useful to see your problem firsthand, does 1:00PM sound OK?
This is affecting me as well. We have a large number of operational reports and it's not feasible to go through them all and make the change unfortunately.
Update: Further, if the file is opened in 2.8 with stale data, all the Category fields are classified as such in data manager. It is only after updating data from source that their type changes.