ChatGPT - Power BI Custom Visual | SHOCKED AND CONFUSED

แชร์
ฝัง
  • เผยแพร่เมื่อ 15 ก.ย. 2024
  • I was pretty shocked when ChatGPT told me there was an existing Custom Visual for Power BI. What happened next confused me even more...
    UPDATE: there was at least one custom visual we found that was for Power BI linked into ChatGPT, however, when testing, it was not accurate enough to do an analysis.
    Like and subscribe to see more content I've been working on with ChatGPT and the Microsoft Power Platform. Thanks for watching!
    #ChatGPT #PowerBI #Data #AI #SomeGuyNamedChris

ความคิดเห็น • 6

  • @ChatPowerBI
    @ChatPowerBI 8 หลายเดือนก่อน +2

    👀 I'm coming 🚀

  • @arbaazm3761
    @arbaazm3761 ปีที่แล้ว +1

    There is a Chatgpt visual in powerbi I've seen on Acterys TH-cam channel but even I'm curious to know how!!!!

    • @chrishowell5082
      @chrishowell5082 ปีที่แล้ว

      You are correct, I found that one as well. I did some testing and am hopeful for future updates for sure.

  • @dkangel121
    @dkangel121 ปีที่แล้ว +1

    I wrote a custom Visual a couple years ago. Can it be done, yes. Will I do another one - Unsure yet. Problem is it requires you to use api key in which I am not exactly keen on people using my API key or even risking putting it out there so its kind of a non starter on that front. Even if I used a secondary website to mask my api key it would still pose the issue that people are using my api key. Unsure how Acterys has implemented theirs yet.

    • @someguynamedchris
      @someguynamedchris  ปีที่แล้ว +1

      That's awesome you wrote a custom visual. I think there are ways to use the settings and options to have a user put in their API and not utilize yours. I don't know all of the details of how, but I have seen visuals that had custom entries that did validate.

    • @ChatPowerBI
      @ChatPowerBI 8 หลายเดือนก่อน

      A backend will be needed to generate keys for each developer and control how much token each uses. Even so, the developer's key will be exposed on the frontend (published report). To get around this there are some strategies. In our case, the backend has a policy of allowed origins (URLs) that can call the endpoint, in this case, only the developer report URL that can call the endpoint. So, even if the key is known to third parties, they will not be able to use it.