Appreciate that Dataflows is currently in Preview so not expecting everything immediately. Could I just ask the following;
This is a possible bug - After setting up Incremental refresh on the dataflow it automatically creates the necessary RangeStart and RangeEnd parameters and adds a step to titled #"AgentByTeamBySkillByDay-54686544617465-autogenerated_for_incremental_refresh". Renaming this step for readability and placing it earlier in the list of steps causes a new auto generated incremental refresh step to be added.
Hi Mark, the autogenerated step for incremental refresh (in this case #"AgentByTeamBySkillByDay-54686544617465-autogenerated_for_incremental_refresh") should remain as is - without renaming it or placing it earlier in the list of steps.
For the Custom Column - you can also create it in Power BI desktop using the interface, then just copy the Advanced editor code out, and into Dataflows.
To me that seems easier than messing with non-intellisense M language.
Twice my searches have led me to this thread - similar problems seemingly.
Another vote for adding 'Folder' as a Datasource option. Is it meaningful to start suggested-votes for these, or no since parity is the goal anyway...?
@mmace1 Just thought I'd mention that I've done some testing with a folder data source and PBI dataflows and it is possible to get it working.
You need to connect to the Folder data source in PBI Desktop and then copy each of the querries, along with the parameter and function from the Advanced Editior in PBI desktop in to a Blank query within dataflows. The only thing I had to do was to remove the Filtered Hidden Files step within the final query
Be great if MS add it as a source so the process is automated but this is an acceptable work around.
As I described in the post below, I have an issue where I cannot save a dataflow containing queries/parameters/function to get csv data from a folder - do you know if there is a way to fix it?
Thanks in advance.