Lookup Activity Refencing file in different workspace

[MartinMason]

We have a medallion architecture. Our bronze layer consists of two workspaces for the different source systems being combined. We have a third workspace for the gold layer combining conformed data from the two separate source systems. We would like to create a single Master pipeline that orchestrates the entire ETL process in the Gold workspace. However, a Pipeline Activity cannot call a pipeline in a different workspace. So no go there. So we thought we'd move the master pipelines from the Bronze workspaces to the Gold workspace to workaround that limitation. Now when a Lookup activity is executed for the bronze master pipeline which reads a configuration file from the bronze lakehouse, it blows up. Is this a temporary glitch? All lakehouses in our tenant are listed as options in the initial configuration of the Lookup Activity so one would think that you'd be able to reference a lakehouse file.

[Anonymous]

Hi @MartinMason ,

Thanks for using Fabric Community.
Can you please check this similar thread: execute activities in another workspace? - Microsoft Fabric Community
I hope you might some insights while looking this thread.

Please let me know if you have further queries.

[MartinMason]

Not useful in my case. Microsoft needs to gather around and get on the same page. Best practices as I understand them, is that medallion layers should be placed in separate workspaces. Bronze layer, or layers in my case, and gold in different workspaces.

However, Pipelines do not enable that to be accomplished, at least by orchestrating load of Bronze layer followed by Gold in a single master pipeline. When creating an Invoke Pipeline activity, only Pipelines in the current workspace can be referenced. Come on, Pipeline team, get your #### together.

Workaround, have Pipelines all be in the same workspace and call Lakehouses in other workspaces to populate Bronze. Though a Copy Data activity can reference a Lakehouse in a different workspace, and Validation will succeed, execution of that Copy Data activity will fail with the following.

Failure happened on 'destination' side. ErrorCode=LakehouseOperationFailed,'Type=Microsoft.DataTransfer.Common.Shared.HybridDeliveryException,Message=Lakehouse operation failed for: Operation returned an invalid status code 'NotFound'. Workspace: 

I'm interpreting this as the Copy Data activity is looking for the specified Lakehouse in the current workspace as nowhere in the Copy Data activity is a workspace able to be specified. This "feature" of the Copy Data activity is truly an epic fail.

[Anonymous]

Hi @MartinMason ,

I would like to understand how are you connecting to the lakehouse present in different workspace via Copy Activity? If you can share these details, I can guide you better!

[Anonymous]

Hi @MartinMason ,

We haven’t heard from you on the last response and was just checking back to see if you got a chance to check my last response.

Thanks

[Anonymous]

Hi @MartinMason ,

We haven’t heard from you on the last response and was just checking back to see if you got a chance to check my last response.

Thanks