Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

Data Days is here! Join us now for 60+ days of learning, challenges, and connection. Learn more

Reply
Anonymous
Not applicable

Why doesn't IFERROR work for PATH errors?

There are several posts on dealing with errors that occur when using the PATH function in DAX.  All of the ones I've seen focus on fixing the data before trying to use PATH.  In my case, I'm using the path to do some LOOKUPVALUE calls to determine other values.  In short, if the PATH fails to find a path for any reason, that's ok.  Given some recent changes in the data, I now get the following error:

The value '1349021' in 'MyTable'[ParentId] must also exist in 'MyTable'[Id]. Please add the missing data and try again.

So I tried the following code to ignore the error:

Parent Path =
  IFERROR (
    PATH (
      [Id],
      [ParentId]
    ),
    ""
  )

My assumption was that IFERROR () would trap the error and allow me to proceed with a blank value.  Why can't errors in the PATH function actually be trapped and handled?  Any help would be appreciated.

 

1 ACCEPTED SOLUTION
Anonymous
Not applicable

Thank you for the information @Anonymous .  The problem needs to be solved in two steps.  Step one is to make a Parent Search Id using LOOKUPVALUE, as follows:

 

ParentSearchValue = 
  LOOKUPVALUE (
    [Id],
    [Id],
    [ParentId]
  )

The LOOKUPVALUE function handles the failures.  Step two is to proceed with determining the PATH, using ParentSearchValue instead of ParentId.

 

View solution in original post

2 REPLIES 2
Anonymous
Not applicable

Hi @Anonymous ,

I think path function analytic on whole field records instead each row. So if these records are not stored as parent child hierarchy, it will return error due to multiple available relationship mapping. 

In my opinion, you can add a calculated column to replace error records and use this column in path function.

Regards,
Xiaoxin Sheng

Anonymous
Not applicable

Thank you for the information @Anonymous .  The problem needs to be solved in two steps.  Step one is to make a Parent Search Id using LOOKUPVALUE, as follows:

 

ParentSearchValue = 
  LOOKUPVALUE (
    [Id],
    [Id],
    [ParentId]
  )

The LOOKUPVALUE function handles the failures.  Step two is to proceed with determining the PATH, using ParentSearchValue instead of ParentId.

 

Helpful resources

Announcements
Fabric Data Days is here Carousel

Fabric Data Days 2026

Don't miss out on Data Days, June 15 through August 7. Learn Fabric, Power BI, SQL, AI and more.

May Power BI Update Carousel

Power BI Monthly Update - May 2026

Check out the May 2026 Power BI update to learn about new features.

Power BI DataViz World Championships carousel

Power BI DataViz World Championships - June 2026

A new Power BI DataViz World Championship is coming this June! Don't miss out on submitting your entry.