Has anyone found a better way to resolve this issue?
Seems like other folks have had the same issue in the past under different versions of the desktop application and the only workaround was rolling back to a prior version. My theory is it has to do with the new data format and/or the latest version of PBI Desktop. I don't know if this is a function of the new enhanced metadata format or not. If I retroactively hardcode one of the parameters, replacing its occurrence in all instances but keeping the other parameter in each query where it's used as an argument, then the "Discard Changes" dialogue tells me that the change is then occurring with the other parameter. Selecting "Discard changes" indicates that I've changed something about the parameter:Ĭlicking "Discard" appears to have no effect whatsoever and the warning notification persists at the top of the report canvas pane. Selecting "Apply changes" appears to apply a transformation to "Queries Metadata":īut as soon as its loaded the warning notifcation to apply or discard immediately appears again. #"fp_SharepointArtifact" = Sourceĭespite the query editor successfully being able to ETL the desired files, upon selecting "Close and Apply", the changes appear to go into effect, but then the warning notification "There are pending changes in your queries that haven't been applied" appears at the top of the report canvas pane with the options to "Apply changes" or Discard changes": Source = SharePoint.Files( PBISharepointBudgetWorkspaceURL), I have been running into issues when I attempt to use parameters in an M-query to retrieve and transform data from a Sharepoint site in custom M queries created from the "New Source" -> "Blank Query" function in the Query Editor's UI.Ī collection of queries currently uses two different parameters, one for the URL to the Sharepoint Workspace and one for the URL to the desired file's directory on the SP site: "Store datasets using enhanced metadata format" IS enabled in Preview Features.
0 kommentar(er)
