Power BI

User-defined functions are valuable resources for DAX developers. By creating functions, developers can compartmentalize model code into smaller, manageable segments that facilitate independent testing and debugging. After thorough validation and optimization, each function becomes a building block that contributes to the overall robustness of the project.

Functions can be used to share a common business logic within a semantic model, as well as between different models. You can get libraries of DAX user-defined functions at https://daxlib.org/,

To avoid confusion, we always use Pascal case for user-defined functions.

When defining parameters, we have the option to choose the parameter type, subtype, and parameter-passing mode. The most crucial detail is the parameter-passing mode; we dedicate a specific section to this topic later on in the chapter. There are two parameter-passing modes, and the choice of parameter-passing mode significantly impacts the function’s behavior. In contrast, the parameter type and subtype are less relevant. The parameter-passing modes are: VAL: Short for Value. Indicates a parameter that is evaluated before the function call, in the evaluation context of the caller. A VAL parameter has a single and well-defined value during the execution of the function body. Multiple evaluations of the same parameter always produce the same result. EXPR: short for Expression. Indicates a parameter that is an expression, evaluated in the evaluation context where it is being used in the function body. Multiple evaluations of an EXPR parameter may (and oftentimes do) lead to different results.

Recursion or mutual recursion is not supported.

Optional parameters are not supported.

Although UDFs can be used in live connect or composite models, there is no IntelliSense support.

References to a tabular model object (e.g. measure, table, column) in a UDF are not automatically updated when those objects are renamed. If you rename an object that a UDF depends on, the function body will still contain the old name. You must manually edit the UDF expression to update all references to the renamed object.

The ability to view Power BI files directly in OneDrive and SharePoint preview requires Power BI Admins to opt-in to enable the preview. The ability to share links to Power BI reports saved in OneDrive and SharePoint from Power BI Desktop preview is on by default and requires Power BI Admins to opt-out to disable the preview.

If a user is new to Power BI, they can quickly become overwhelmed. This is especially true if your app has grown to include many sections, reports & dashboards. Giving users access to a “Tutorial” or “New to Power BI” Audience can help this. If they click on this Audience, it could limit the app to a single report meant to teach the basics of Power BI - slicers, filters, reset-to-default, cross-filtering… etc. This report can be hidden for all audiences, but is revealed when they select the Audience for a tutorial.

It’s common for many software solutions to offer access to a ‘preview’ or ‘beta’ build. Why can’t we do the same with our reports?