Forum Discussion

nick-evans's avatar
nick-evans
Advocate I
8 years ago

PATH throws unexpected exception

I have been struggling to get the PATH formula to work for me because of duplicate names in my data (in case you have seen my handful of other threads related to this).  I finally was able to update...
Need Help
v-ljerr-msft's avatar
v-ljerr-msft
Microsoft Employee
8 years ago

Hi nick-evans,

 

Could you post your table structures with some sample/mock data which can help us to reproduce this issue? It's better that you can share a sample pbix file which can reproduce the issue. You can upload it to OneDrive or Dropbox and post the link here. Do mask sensitive data before uploading. :smileyhappy:

 

Regards

  • Cymbolz's avatar
    Cymbolz
    Helper III
    8 years ago

    I've encountered example the same issue.  

     

    I have a table of staff with a staffID and email.  There is a report-to column indicating who their manager is.  If I use PATH on the numeric staffID columns it works (new calculated column with expected values that PATH has determined).  

     

    But I want to create the path output based on email, so created a column for managers email using dax lookup.  Then tried path on the email columns and got the error.

     

    Am guessing either - it's the calculated column causing the issue, or text.  As it works with numerics per the columns coming purely from the query.

     

    Any ideas / solutions?  I can provide more details if required.