Monday, August 14, 2023
2 changes · master
Enhancements to existing features
Users can now share dashboard views directly from the spreadsheet interface, making it easier to distribute insights without switching tools. This improves collaboration around dashboards and streamlines the workflow for teams using spreadsheet-based reporting.
Original PR description
This PR implements the sharing of dashboards from spreadsheet view.
Grid views now handle row titles and missing measure fields more reliably, reducing errors in timesheet and web grid screens. Custom grid buttons also correctly stay hidden when their visibility rules say they should, improving consistency for users.
Original PR description
## [IMP] account_consolidation: add test for consolidation grid view ## [FIX] web_grid: hide custom button if invisible = true Before this commit, when the custom button should be invisible when a…
## [IMP] account_consolidation: add test for consolidation grid view
## [FIX] web_grid: hide custom button if invisible = true
Before this commit, when the custom button should be invisible when
a context is not there or falsy, the custom button is always displayed
because the `invisible` modifier is not used to conditionally display
the custom button.
This commit adds a visibility condition to display the custom if
invisible modifier is falsy, otherwise the custom button is not
rendered.
## [IMP] {web,timesheet}_grid: add grid_component to use it in row title
Before this commit, the row/section title was rendered with components
in `fields` registry but we have to use `Record` component to be able
to use those components since `record` is needed.
This commit creates some grid components to be able to use it in
section/row title to avoid using the `fields` registry and Record
component in grid view.
## [IMP] web_grid: avoid using parseFieldNode in grid arch parser
Before this commit, `parseFieldNode` from Field component was used
to get label for measure field, to get widget and invisible values.
This commit avoids using it and search the attributes needed directly
on the node because `parseFieldNode` also search the field component
to use but in the grid view it is not needed since the field registry
is no longer used for section and row fields.
## [FIX] web_grid: fallback on count measure if no measure field
Before this commit, when a grid view is defined without any measure
field in its definition, a traceback is occured because the "__count"
field is not inside the fieldsInfo which is expected.
This commit reviews the measureField attribute in archInfo to
determine if the field is readonly or not and then improves
editable attribute in archInfo to determine if the grid view
can be editable or not including the readonly attribute of
measure field. By doing that, it is no longer needed to check
the field inside fields info in the grid controller.
task-3222154