Forum Discussion
Memorable MemberWhich focused table when editing/opening a gen2 dataflow?
Super UserHi dbeavon3
I think based on my experience this happens to always keep the first table that was created. The only thing I can think of is to use a parameter to not return all the information from your table. This is so that when the dataflow opens it will only get a subset of the data?
Memorable MemberHi GilbertQ
The parameter option is pretty good, however the most problematic environment is production. In production we aren't using a subset of data. In the chance that we need to open the dataflow in production for review or for troubleshooting, then it will send an uncontrollable torrent of queries to our back-end systems. (Everybody hates it when PBI developers are opening their datasets and dataflows to review something in production.)
...On that note, you don't happen to know if PQ has ever introduced any sort of context/environment information that can be inspected to see if I'm in my "IT-DEV" workspace or in my "IT-PROD" workspace? This type of thing would greatly simplify some of these problems. I suppose your answer to that is to have a parameter for it, and manually edit it, every time we deploy from one environment to another.
IMO, PQ rarely seems to have features that most normal developers would expect. Thankfully I only spend about 5% of my time doing PQ development work but it is never fun or productive. It is not an "easy" software development experience either, whatever the product team may say, unless we happen to be working with something trivial like 100K rows of data or less.