Variable library usage leads to error with dynamic data destination

[JamesMurkin1]

Hi,

I am trying to use a dataflow to load data from an external PostgreSQL database into a Lakehouse. I have dev, test, and prod workspaces created and linked through a deployment pipeline, with identical lakehouses in each. Therefore, as the dataflow goes from one workspace to the next, the destination needs to be managed accordingly (as it doesn't automatically update as part of the deployment process).

I have tried using a variable library (based on this documentation) that contains the Workspace and Lakehouse IDs for each stage, but run into an error.

I create the WorkspaceID variable using this query (with an equivalent one for the lakehouse ID), and disable staging:

This produces the expected value:

However, as soon as I add a table, I get the following error with the variables:

The import Variable.ValueOrDefault matches no exports. Did you miss a module reference?

Details

Reason = Expression.Error

ErrorCode = 10079

Any help would be appreciated - thanks!

[miguel · Accepted solution]

hi!

Would you mind confirming a few things, please?

- is your Dataflow a Dataflow Gen2 (CI/CD)?

- are you perhaps using a Gateway? If yes, what version is the gateway?

[JamesMurkin1]

Hi!

Thanks for the reply.

I've updated the gateway to the latest version (March 2026, was previously from July 2025) which looks to have fixed this issue. Didn't see that anywhere in the documentation so I'm glad you've pointed it out.

Thanks 🙂