| |||
| Resolving the problem | |||
| A view publish produces a number of different views for different purposes. Specifically, fv_cubename does not contain data for aggregate nodes, it is designed for reporting tools that perform their own aggregation. The ev_cubename view holds data for both aggregate and leaf nodes. More details on the different views can be found in the 'Publishing Data' chapter of the Contributor Administration Guide. |
Purchase your Section 508 Compliance Support guide now!
The table published from Contributor doesn't contain data for any nodes that aggregate data from their subnodes
The table published from Contributor doesn't contain data for any nodes that aggregate data from their subnodes
| |||
| Resolving the problem | |||
| A view publish produces a number of different views for different purposes. Specifically, fv_cubename does not contain data for aggregate nodes, it is designed for reporting tools that perform their own aggregation. The ev_cubename view holds data for both aggregate and leaf nodes. More details on the different views can be found in the 'Publishing Data' chapter of the Contributor Administration Guide. |
Unable to change an attribute that has a fact usage to have no aggregate property.
| |||
| This can be done by setting the attribute usage to unknown and then redetermining usage on the attribute In the Project Viewer pane, select one or more query subjects. In the Properties pane, change the following values -
From the Actions menu, click Determine Usage to leave the aggregate properties to unsupported. |
Unable to change an attribute that has a fact usage to have no aggregate property.
| |||
| This can be done by setting the attribute usage to unknown and then redetermining usage on the attribute In the Project Viewer pane, select one or more query subjects. In the Properties pane, change the following values -
From the Actions menu, click Determine Usage to leave the aggregate properties to unsupported. |