The refresh history does not show the duration in h, m, s. I can manually calculate the difference by comparing the Start and End dates, but that is a lot of work when I have a long history. I should be able to get this information at a glance to help identify outliers and to understand the average and median values.
3 Comments
- vinay_murliNew MemberI came here to submit a different idea; but while searching existing ideas (to make sure I don't create a duplicate), I came across this. I agree. Currently for Dataflows, the user can simply right-click on an individual Dataflow; and the resulting menu contains Refresh History. (So the user is able to access the Refresh History in 2-mouse button clicks). Then when the user proceeds and selects this Dataflow Refresh History, it pops up over the same page, and it shows the Date/Time the Refresh was launched and the Duration (hh:mm:ss). Then when done reviewing, the user can simply close this popped up window (1-mouse-button-click), and they are right back on the Workspace Main Page. Meanwhile for Dataset Refresh History, a user must right-click and select Settings. This jumps the User to a different page. Then the user must click on Refresh History. (This is 3 mouse-button clicks). Then when the user views the Refresh History, the displayed information is inferior to the way the information is displayed in the Dataflow Refresh History. The user needs to manually/mentally calculate the End-Start Date/Time to determine the Duration (as described by the original poster of this idea above). Finally, the user must Close this window and then do another click to get back to the Workspace Main Page (2-mouse-button clicks). In a nutshell, please conform the Dataset Refresh History to be equivalent to the existing Dataflow Refresh History. This will resolve the Idea by the poster above. I will possibly be submitting this as a separate Idea.
- GTHOMANNNew Member
If you are here ... then you may want to go to the link below on the 'help' forum to also vote for similar bug/idea posts. Thanks.
- fbcideas_migusrNew MemberStatus added:Needs Votes
Recent ideas
Clone a workspace, including its data, to a new workspace
Description: Today there's no way to fully clone a Fabric workspace: git sync and Deployment Pipelines move item definitions only, not the underlying data; Warehouse's zero-copy CREATE TABLE ... AS ...gclements8 minutes agoHelper IINew2Views0likes0CommentsAllow NotebookUtils getSecret() to authenticate with Workspace Identity
Current behavior In Microsoft Fabric, notebookutils.credentials.getSecret() authenticates against Azure Key Vault using the identity of the user who executes the notebook. This behavior appli...tmihara5 hours agoNew MemberNew5Views0likes0CommentsSupport Synonyms in Fabric Warehouse
Microsoft SQL Server has a very powerful feature by the way of "synonyms." It allows users and DBAs to do all sorts of powerful magic such as rewiring objects under the hood (e.g. run the code agains...matthias-bi9 hours agoRegular VisitorNew1.3KViews18likes2CommentsExpose Refresh Warnings and Informational Messages via Notifications and API
When a Power BI semantic model refresh completes successfully, the status shows Completed, even when the refresh details contain warnings or informational messages that require attention. Please pro...Jashwanth_K11 hours agoMicrosoft EmployeeNew24Views6likes0CommentsInvoke Pipeline Task - Workspace Identity Authentication
Currently, the Fabric Data Factory Invoke Pipeline task uses the user's credentials who saved the pipeline to then authenticate to the Azure Data Factory to execute the ADF pipeline. When that user'...dzebrowitz15 hours agoAdvocate IPlanned1.8KViews61likes5Comments