This page has 0 threads | Add post

Blogs

Finding our blogs useful? Please consider helping us to share more!

Debugging (sort of) in DAX
Learn to use DAX variables, and understand how they can be used to break up code. Not true debugging, but better than nothing!

Posted by Sam Lowrie on 30 July 2018

Debugging (sort of) in DAX

This is another tip via the DAX wizard Marco Russo, this time about tracking errors in your code. Consider this long winded code to paginate tables:

It'll be a pretty grim job to try and work out what it does. The code is from my blog on creating pagination in tables.

While this formula might look impressive, it is difficult to follow and even harder to find where an error occurred. By a huge coincidence there was one:

Let's face facts: Microsoft error messages aren't always the easiest to decipher, and we haven't made it any easier!

What would make this clearer would be to break the long formula into two or more separate measures. However, dividing a single measure like this into separate ones can change its functionality (not to mention creating clutter!). We need a single-measure solution!

Variables

Enter the DAX variable, which allows us to create a measure within a measure. To create a variable enter VAR followed by a name and an equals sign:

The Return command is used at the end of the measure to return a value. No return, no numbers!

The above isn't going to help much but, it does give the outline for using variables. Now I want to split the code into separate functional parts:

Whilst I might still be getting an error, how much nicer is this to read!

Now for the cool part. Instead of returning the final value, comment it and all other variables out bar the first one. Put the first variable next to the Return:

The error is gone! This means that it isn't caused by any DAX for the first variable. It also lets me check the variable is returning what I expected.

I can now repeat the process, un-commenting the next variable and returning it until I find the error. Turns out it was actually the very last step that was causing the error:

So between my variable PageNumberV and Final_Value there is an error due to the wrong data type.

It's simple enough to fix this with a little FORMAT function:

Instead of making the Final_Value more complex, I snuck in another variable.

There it is, debugging DAX using variables. Whilst it would be nice to have a true debugger like VBA, this is currently what we have, and using variables will improve your code!

Some other pages relevant to the above blog include:

This blog has 0 threads

Add a new post

Head office

Kingsmoor House

Railway Street

GLOSSOP

SK13 2AA

London

Landmark Offices

99 Bishopsgate

LONDON

EC2M 3XD

Manchester

Holiday Inn

25 Aytoun Street

MANCHESTER

M1 3AE

Site map

Terms & Conditions

Book any course as classroom, onsite or online training, or as one-to-one consultancy

Free resources

Paid services

Getting help

Where we are

Where you are

Online

Transparent reviews

Delivery of courses

Nicer to work with

Reliable and established

Our training courses

C#

Excel

MySQL

Power Apps

Power Automate

Power BI and DAX

Python

Report Builder

SQL

SQL Server

VBA Macros

Other training resources

Blogs

Exercises

YouTube tutorials

YouTube shorts

Test your skills

Consultancy

Courseware

Self-paced courses

Newsletters

Publications

Our training venues

London

Manchester

Across the UK

At your site

Online

Why we are different

Hundreds of published reviews

Small class sizes

Outstanding courseware

Online classroom

(Almost) no cancellations

Wise Owl trainers only

Genuine integrity

Invoices after training

30+ years of Wise Owl

Our top 100 clients

BLOGS BY TOPIC

BLOGS BY AUTHOR

Debugging (sort of) in DAX

Variables

Head office

London

Manchester