Invoke Pipeline Returns "Could not found the requested item"
I'm having issues with the Invoke Pipeline(Preview) activity where I am getting the error {"requestId":"e9e54d07-8d30-4de4-b3f4-3be3ad15a476","errorCode":"ItemNotFound","message":"Could not found the requested item"} To test this issue, I set up a: A pipeline with the only activity in it being Invoke Pipeline(Preview) No parameters - The original pipeline I set up had parameters and I was getting the same error code so I tried to remove it to see if it was a parameter issue A child pipeline with the only activity in it to Get Metadata for a table in a lakehouse No parameters This pipeline will successfully run on its own When I run #1 I get the error message {"requestId":"e9e54d07-8d30-4de4-b3f4-3be3ad15a476","errorCode":"ItemNotFound","message":"Could not found the requested item"} however I'm not sure why the Item would not be found since I was able to specify it. I am attaching my configuration settings as screenshots to this post. Did I miss something in the Invoke Pipeline settings? Parent Pipeline Child Pipeline
Evolving the ADF to Fabric migration experience
Hi team, When working with Azure Data Factory and moving into Microsoft Fabric, the new “migration” experience is a really interesting step forward. It helps bring both worlds closer and makes the transition smoother. After trying it out, I’ve seen that it opens up a lot of possibilities, and it’s great to see that we can also propose ideas to continue improving it. In this context, I’ve shared an idea that I believe could bring even more value. Right now, the experience allows you to connect and integrate existing ADF assets into Fabric, which is very helpful to start working within the ecosystem. As a next step, it could be interesting to move towards a deeper integration where: Assets are fully integrated into Fabric They are executed from Fabric And their consumption can be associated with Fabric capacity Additionally, it could be valuable to give customers the flexibility to choose where the cost is allocated (Fabric or Azure), enabling a more gradual adoption. This is a small evolution on top of what already exists, but it could make a big difference in how the experience aligns with different adoption scenarios. If this idea resonates with you, you can vote for it here: https://lnkd.in/ejT9QSRj And if you find it useful, I would really appreciate your support with a like on the comment and voting for the idea. This helps increase visibility and gives it a better chance to evolve.Dataflow Gen2: Variable Library references fail in Connection Settings
Hi everyone, I am working on variabilizing my Dataflow Gen2 for deployment pipelines, following the documentation on Variable references. I’ve noticed a discrepancy in how variables are handled, and I suspect it might be a bug or a UI limitation. The Issue: When I define parameters using a Blank Query and try to use them to replace values in the Source Connection settings (via the user interface), the connection fails or isn't recognized. And replace in the source: let Source = Lakehouse.Contents([]), #"Navigation 1" = Source{[workspaceId = workspace_id]}[Data], #"Navigation 2" = #"Navigation 1"{[lakehouseId = lakehouse_id]}[Data], #"Navigation 3" = #"Navigation 2"{[Id = "Table1", ItemKind = "Table"]}[Data] in #"Navigation 3" That's not working. The Workaround (Manual M Code): However, if I bypass the UI and manually insert the Variable.ValueOrDefault syntax directly into the Source Step using the Advanced Editor, it works perfectly. let Source = Lakehouse.Contents([]), // Retrieving variables manually works fine workspace_id = Variable.ValueOrDefault("$(/**/My Library/Workspace ID)", "default_value"), lakehouse_id = Variable.ValueOrDefault("$(/**/My Library/Lakehouse ID)", "default_value"), #"Navigation 1" = Source{[workspaceId = workspace_id]}[Data], #"Navigation 2" = #"Navigation 1"{[lakehouseId = lakehouse_id]}[Data], #"Navigation 3" = #"Navigation 2"{[Id = "Table1", ItemKind = "Table"]}[Data] in #"Navigation 3" My Question: Has anyone else encountered this issue where the UI connection dialog doesn't seem to parse the variable reference, forcing us to hardcode M logic manually? Is there a specific syntax for the UI that differs from the Advanced Editor? Thanks for your help! References: - Dataflow Gen2 Variable Library Integration
A Typo in the new parameter window of Dataflow Gen2 (Korean)
Hi Team, When I tried to create a parameter in the Dataflow Gen2, I noticed a typo in the new parameter window: 어느하나라도 The labels were different from Power BI Desktop. In Dataflow Gen2, that should be modified as follows. 어느하나라도(Any) -> 임의 Korean English Power Query editor (Power BI Desktop 2.146.705.0 64-bit (August 2025)) Korean English Thanks, Hong
