How to configure Copilot Studio to check ServiceNow KB and then External KBs

แชร์
ฝัง
  • เผยแพร่เมื่อ 10 พ.ย. 2024

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

  • @FirmResultsInc
    @FirmResultsInc 7 หลายเดือนก่อน +1

    Awesome! Thank you for sharing this updated version. Not only does it reflect the actual UI, the second phase is a cool new feature.

    • @Dewain27
      @Dewain27  7 หลายเดือนก่อน

      Glad you like it!

  • @asgaskins
    @asgaskins 7 หลายเดือนก่อน +1

    Fantastic material as always Dewain. Thank you for taking the time to continue our education!

    • @Dewain27
      @Dewain27  7 หลายเดือนก่อน

      My pleasure!

  • @PowerPlatformDoug
    @PowerPlatformDoug 4 หลายเดือนก่อน +4

    Hi Dewain - been in the Power Platform / D365 space for a long time, but new to Copilot Studio and your videos have been excellent to help me get up to speed. This stuff is changing at such a rapid pace, it's not feasible to constantly update videos as changes get pushed. I'm sure you know this, but wanted to call out in case anyone else runs into this. Since you posted this video, the ServiceNow connector has been updated to output both a meta record and an articles table and no longer outputs the 'result' record. I followed all the steps as is in the video with the exception of the variable definition step. All I changed for it to work was remove the 'GetKnowledgeArticles' piece out of the ForAll. "ForAll( Topic.articles, {Content: Concatenate......"

    • @timwYoutuber
      @timwYoutuber 2 หลายเดือนก่อน

      would love to have your full function

  • @neilokelly9208
    @neilokelly9208 7 หลายเดือนก่อน

    Dude your amazing !!! this is excellent, thanks so much. We use service now and my bosses are 100% going to want this.

    • @Dewain27
      @Dewain27  7 หลายเดือนก่อน

      Glad I could help!

  • @RiteshRajWaghray-i4w
    @RiteshRajWaghray-i4w หลายเดือนก่อน

    Sir good one . But in latest Copilot Studio the Custom Connector option is not there anymore in the GenAi node for SnowKB reading. What is the options then., ????

  • @ashwariyasah-f9b
    @ashwariyasah-f9b หลายเดือนก่อน

    Hey Dewain,
    Thanks for the awesome video. The issue I am facing is with URL, my url from servicenow uses & and power fx auto encodes it. I am stuck on this for a week, any suggestions

  • @nerdintech
    @nerdintech 2 หลายเดือนก่อน

    Is there a way to do it and bring the link from the article? I also tried bring the articles through Microsoft Graph, but its not working... i ask for microsoft support but they did no answerd.

  • @MaksymLinnik-l1i
    @MaksymLinnik-l1i หลายเดือนก่อน

    Please advise. If I send the bot a ticket number that is on the serviceNaw, can the bot return the ticket information?
    Thanks

  • @lindsayshelton7162
    @lindsayshelton7162 7 หลายเดือนก่อน

    Hey Dewain! I loved your video and will be following it religiously about connecting Copilot Studio to ServiceNow KBs and then external fallback sources. I had a question that wasn't answered in the video that I hoped you could help me with. So to create the connection, it says we need a username and password for that instance. I would assume we want to do this with a ServiceNow service account, but what levels of permissions and licensing are required for it to just fetch the KB articles? Thanks so much in advance!

    • @Dewain27
      @Dewain27  6 หลายเดือนก่อน +1

      I am not someone that can answer ServiceNow licensing questions... sorry. You could do the pulling of the data with a bearer token if you wanted, but that is something too complicated for most people to understand in a video. I might do something advanced like that in the future, but might have to make a different playlist for it as you are getting into pretty deep AUTH concepts.

  • @thedatascientist-lg4ls
    @thedatascientist-lg4ls 6 หลายเดือนก่อน

    Fantastic video Dewain! What about connecting your Copilot to internal databases on SharePoint? Can the datasource be automated using Power Automate in connection to the Copilot?

    • @Dewain27
      @Dewain27  6 หลายเดือนก่อน

      I don't think I would need Power Automate to do it... I have direct connector access. I would have to determine the way to search the SharePoint KB. In what format is it in for SharePoint?

  • @jeamibasco4931
    @jeamibasco4931 7 หลายเดือนก่อน

    As always. Great content

    • @Dewain27
      @Dewain27  7 หลายเดือนก่อน

      You do it with the filter on the connector. More details are in the API reference: developer.servicenow.com/dev.do#!/reference/api/utah/rest/knowledge-management-api

  • @huyfe1347
    @huyfe1347 7 หลายเดือนก่อน

    Awesome. Thank for this video. Any chatbot use case with voice use and transcription into text and connexion to CRM?

    • @Dewain27
      @Dewain27  7 หลายเดือนก่อน

      Not yet... :-)

  • @mikkok.4245
    @mikkok.4245 7 หลายเดือนก่อน

    I keep getting "Requested URI does not represent any resource" with the Get Knowledge Article actions. I can use the List Records action with the same connection, but I keep getting the error with the Get Knowledge Article one. Do you have any ideas about what I might be missing?

    • @Dewain27
      @Dewain27  7 หลายเดือนก่อน

      Ahh you have to add the knowledge API plugin in ServiceNow. developer.servicenow.com/dev.do#!/reference/api/utah/rest/knowledge-management-api

  • @LexysHereAfter
    @LexysHereAfter 6 หลายเดือนก่อน

    I followed these steps but I have a couple of things that don't quite function the way you're showing. The results show the top 3 results and just a snippet of the body of the KB articles rather than showing the top result with the instructions clearly shown.
    The link to the SN Instance isn't working because it shows the copilot URL infront of the ServiceNow URL

    • @Dewain27
      @Dewain27  6 หลายเดือนก่อน +1

      There is a formula that constructs the table. In that I make the URL to the article. Don't use the snippet use the body in what you pass into the table as well.

    • @LexysHereAfter
      @LexysHereAfter 6 หลายเดือนก่อน

      @@Dewain27 ah perfect that makes it much more usable for our purposes