Variable Library

Hi Ira_27​ ,

Thank you for reaching out to Microsoft Fabric Community Forum, Below are the few points which can resolve your issue. Let us know if you need any further assistance.

• The behavior shown is expected when dynamic content is used for the Warehouse connection. Fabric switches from the normal connection selector to the parameterized connection fields.
• For the Lookup activity, don't pass the Variable Library Connection Reference directly into the connection field.
• Instead, store the required connection properties as separate Variable Library variables:
  • Warehouse ID / Connection ID
  • Workspace ID
  • SQL connection string, if required
• Reference those variables individually through Dynamic content in the corresponding Lookup fields.
• For Notebook activities, Connection Reference variables can be handled differently using the supported Variable Library/notebookutils approach.
• Item Reference variables should be used for Fabric item references (such as Workspace/Item IDs), rather than treating them as a generic connection object.
• If the Lookup UI still clears the configuration after parameterization, test the same setup with pipeline parameters first. If that works, the issue is specifically with Variable Library integration rather than the Warehouse connection itself.
• Also make sure the referenced Warehouse and workspace are accessible using the same identity/connection configuration at runtime.

Thanks,

Chaithanya.