A Small Gotcha with Fabric UDF Parameters

When building a function explorer in Python for Fabric, everything worked fine during local testing, but publishing the UDF failed.

The reason? Fabric enforces stricter rules on UDF input parameter names than the test environment does. Specifically, input parameters cannot contain underscores (_).

When testing translytical features in Fabric, especially using the new Functions explorer, these stricter naming rules apply, so what works locally might not publish successfully. Renaming parameters (e.g., start_time → startTime) fixed the issue immediately.

This is a small but important detail that can save time and frustration when trying out the new Functions explorer.

3 comments