on
RE:
TERA BAAP HU ME TERA BAAP HU ME TERA BAAP HU ME
RE:
have a look at COALESCE
RE:
TERA BAAP HU ME TERA BAAP HU ME TERA BAAP HU ME
RE:
Yes, and it would be great at the column level so that we have control of where it appears: set a summarize aggregation of "Count in summary" for a coumn so that it shows the data in the grid, but a count in the totals section. We currently have count columns all showing 1, which is silly.
RE:
Tip - If you go into advanced editor, you can add a //comment line before any step. This appears in the UI as an ⓘ icon next to the step.
RE:
Note - you can get this from Azure adminstration: https://admin.microsoft.com/Adminportal/Home?source=applauncher#/licenses
RE:
In a similar way I suggested adding a flexbox container for visuals, so that they can be automatically arranged without needing to carefully drag them around the design-surface. Have a look at https://ideas.fabric.microsoft.com/ideas/idea/?ideaid=8f8cd329-425e-ee11-a81c-00224854aa33
RE:
Yep - that would make explore data so useful, rather than having to save to a report each time. Also would help to not limit export to 150K rows (or 30K for csv).
RE:
/Sigh/ These forums don't format comments properly. *** TL;DR: Improve JSON serialization for true VCS ***
RE:
Thans for collating this, it's a shame it's a bit lost in the ideas forum, but I found it :)My main comment is the last point:Incorportate version control and undo/redo functionalityFor version control - the critical thing here for me is rather than having this incorporated directly in the UI, instead concentrate on making true version control possible.- version control is more than simply going back to an old version (although of course simple undo in the UI is essential)- the real power of version control is the ability to see differences and merge changes across versions.- the standard way to enable this is to ensure there is an underlying representation as text that has had some though applied to make it possible to merge. Think code + git.So can I ask that there is some collaboration with the bookmark changes along with the team that is looking at the report-definition equivalent of TMDL.Currently the report serialization is incredibly granular and verbose, and is impossible to diff+merge.My key improvements would be:One json file per bookmarkReportSection ID can be set by user and remains stableVisual containers ID can be set by user and remains stableA readable DSL grammar for expressions (), rather than a json serializatin of an AST.If there's a place where this is being discussed in more detail, I'd love to contribute.