Using Dataverse as a Knowledge Source in Copilot Studio

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

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

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

    The worst part about using dataverse table as a knowledge source is that you cannot exclude all the technical dataverse columns like ‘Status’, for example. So, in my use case, Copilot keeps referencing that read-only Status column instead of my own Status column that I have in the table…

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

    Silicon Valley, of course!

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

    ❤ thanks for shoutout Bulent ruclips.net/video/UnCEg5JEk0w/видео.html good to see you mix scraping automation with Dataverse prompt. Clever 😉