Forum Discussion
cachedEntity
Anonymous I have not filed a ticket because I am working around the issue. This is something that happens when I use a dataflow as a source inside another dataflow. I am avoiding that scenario for now. While it would be nice to have it resolved, I need to make headway on my project and time is limited.
Hi ebjim
We havent heard from you on the last response and was just checking back to see if you got a chance to create a support ticket. If yes please share the details here. Otherwise, will respond back with the more details and we will try to help.
Thanks
Anonymous I have not filed a ticket because I am working around the issue. This is something that happens when I use a dataflow as a source inside another dataflow. I am avoiding that scenario for now. While it would be nice to have it resolved, I need to make headway on my project and time is limited.
Can you show us the M code for both queries? I have 2 DFs, one being the source for another one. And the data type of one column caused the Power Query engine to automatically insert a line of code that removed this column. Then when my code in the second DF tried to reference this column, I would get a similar error because the column didn't exist anymore because it had been removed from the first DF automatically by Power Query!
Element115 Unfortunately, I got rid of that DF. So, I don't have anything that I can show.
OK... what about the error? Does it appear again with other DFs you are working on or was it a one-off?
