on
RE:
We are developing a series of critical data set to business decision and zooming is a deal break to Shell. Appreciated if this can be prioritized asap!
RE:
I don’t think this is a good idea. It’s too big of a change to the model. If you simply keep to a good dimensional, model can only have measures in your tables. You automatically get the icon that indicates that it’s a fact table you can also use an Amy conventional to use singular for dimensions and plural for fact tables
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).