Find All Errors in All Columns using Power Query in Power BI

Поделиться
HTML-код
  • Опубликовано: 29 дек 2024

Комментарии • 36

  • @Gandalf1969Guy
    @Gandalf1969Guy 7 месяцев назад +6

    OMG so much gold in one small video - thanks Reza! Never did I click on that table icon to get all columns functions plus I did not know about 'Try' function. Great use of unpivot too :)

    • @RADACAD
      @RADACAD  7 месяцев назад

      Thanks. I am glad it is helpful.

  • @christianlira1259
    @christianlira1259 6 месяцев назад +1

    Great way to land on the errors and do something with them. Thank you Reza and much appreciate you putting this video together.

    • @RADACAD
      @RADACAD  6 месяцев назад

      Glad it was helpful!

  • @alexrosen8762
    @alexrosen8762 6 месяцев назад +1

    Extremely useful and well demonstrated tutorial. By far the best one I have seen so far on error handling 👌🙏👌

    • @RADACAD
      @RADACAD  6 месяцев назад +1

      Great to hear!

  • @Softwaretrain
    @Softwaretrain 7 месяцев назад +1

    Thanks Reza, This is a brilliant solution for maintaining clean data without errors while simultaneously having a table that shows which column has errors and what the errors are. Additionally, I think it would be beneficial to unpivot all columns by selecting them all, right-clicking, and choosing 'Unpivot Columns,' since even a key column might have errors.

    • @RADACAD
      @RADACAD  6 месяцев назад +1

      Thanks. Unpivoting everything makes it hard to be able to point back to the record that has the issue, but can be an option sometimes

  • @cezaryczajka9198
    @cezaryczajka9198 7 месяцев назад +1

    Brilliant movie. I spent a lot of time locating bugs. Now it will be easy. Thank you.

    • @RADACAD
      @RADACAD  6 месяцев назад

      Glad it helped 😊

  • @timosborn73
    @timosborn73 7 месяцев назад

    Amazing thanks Reza, you've just conquered the dreaded PQ error message. I was aware of all of those PQ features, but didn't think to use them in that way.

    • @RADACAD
      @RADACAD  6 месяцев назад

      Glad to hear it helps 😊 thanks

  • @sabarashid1513
    @sabarashid1513 7 месяцев назад

    Absolutely amazing, thank you Reza for so many useful information in 11mins video. Thank you for sharing

    • @RADACAD
      @RADACAD  6 месяцев назад

      Glad you enjoyed it!

  • @LIV-FREE-VET
    @LIV-FREE-VET 5 месяцев назад

    Thank you soo much Reza! You are a Power Bi wizard. Can't wait to learn more :)

    • @RADACAD
      @RADACAD  5 месяцев назад

      Thanks. Glad to help :)

  • @janmejayamishra9308
    @janmejayamishra9308 4 дня назад

    Hi Reza, thanks for this video

  • @MuratBarbarosYamak
    @MuratBarbarosYamak 5 месяцев назад

    This is great information. Thanks for sharing!!

    • @RADACAD
      @RADACAD  4 месяца назад

      Glad it was helpful!

  • @DataTorch
    @DataTorch 7 месяцев назад

    Super! Thank you Baraadar 🤠🙏🏻

  • @monikapeppo
    @monikapeppo Месяц назад

    Thanks for the video, very helpful. I have an issue when I publish the report in PowerBi service, the field Custom error details is empty. Do you know if it's a limitation? Thanks

  • @gauravguliani358
    @gauravguliani358 7 месяцев назад

    Simply excellent- missed your videos!

    • @RADACAD
      @RADACAD  6 месяцев назад

      Glad you like them! Thanks 😊

  • @kebincui
    @kebincui 7 месяцев назад

    Excellent 👍👍Thank you Reza 🌹❤

  • @rachidwatcher5860
    @rachidwatcher5860 Месяц назад

    Thank you for the video🙂! when we deal with millions of rows and the errors are far a way from the first 1000 records it become very difficult to find the columns that contain errors. Could you help me to solve this type of problems?

  • @Bondoz007
    @Bondoz007 3 месяца назад

    Hi Reza - I am working with MS Exchange data which I'm using Parameter date to refresh it the data in PBI server only, because it requires a refresh after each PQ step in PBI desktop.
    In the desktop model I work with 1 month - no errors.
    But I get null value can't convert to logical value type error in PBI server
    I am doing a few Group By which I'm pretty sure is causing issues. But so even trying to detect my error using your tips doesn't work.
    When it takes 1 hour for the refresh it's very time consuming.
    If you have any tips for working with MS Exchange data that would be interesting. Thanks 🙏🏽

    • @RADACAD
      @RADACAD  3 месяца назад

      Hi
      Without seeing your PBIX it is hard to see why you get the error. it might be because the date format and your locale. worth trying to convert it by a specific locale as I mentioned in another video.
      However, for exchange's data; although it is possible to get data from it directly using Power Query and bring into Power BI, I suggest to bring that into a data storage option first; something like Dataflow Gen1 or Dataflow in Fabric and bringing it into a Lakehouse or Warehouse first and then Power BI on the top of it. It will make the solution more reliable.

  • @robertomontoya9893
    @robertomontoya9893 2 месяца назад

    Very creative thanks!

    • @RADACAD
      @RADACAD  Месяц назад

      You're welcome!

  • @txreal2
    @txreal2 7 месяцев назад

    Re: import mode file size
    What is the maximum file size in MB that I should start looking at SQL server or direct query? Thanks

    • @RADACAD
      @RADACAD  7 месяцев назад

      The max file size for import depends on your Power BI license, with pro only, it will be 1GB, premium can be up to 400GB depending on SKU

  • @anoopdube9581
    @anoopdube9581 7 месяцев назад

    Fantabulous video

    • @RADACAD
      @RADACAD  7 месяцев назад +1

      Thanks

  • @MrJozop
    @MrJozop 3 месяца назад

    Brialliant!!!!

    • @RADACAD
      @RADACAD  3 месяца назад

      Thanks :)

  • @osamaasif9601
    @osamaasif9601 7 месяцев назад

    Hey Raza, all good man. You look a little under