PL-400 Exam Prep: Deploying a Microsoft Dataverse Plug-in using the Plug-in Registration Tool

Поделиться
HTML-код
  • Опубликовано: 21 окт 2024
  • In this video, I’ll demonstrate how we can deploy out a Microsoft Dataverse plug-in using the plug-in registration tool. Plug-ins are a great tool that developers can use to model out complex business logic that is executed server-side within Dataverse. In this example, we’ll see how straightforward it is to deploy out a plug-in assembly and then test it within a model-driven Power App.
    This video is part of my series focused on providing small, bite-size learning tools to prepare to sit Microsoft Exam PL-400: Microsoft Power Platform Developer. More details about the exam can be viewed below:
    docs.microsoft...
    To view the accompanying blog post to this video, use the link below:
    wp.me/p7cr4U-1OO
    The code for this plug-in was built out as part of a previous video, which you can watch here:
    • PL-400 Exam Prep: Usin...
    Have any questions relating to deploying a plug-in out? Let me know in the comments below, or you can reach out to me on Twitter instead:
    / joejgriffin
    #PowerPlatform #CommonDataService #MicrosoftDataverse #PowerApps #CSharp #DotNet #VisualStudio

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

  • @maxnomicon
    @maxnomicon 2 года назад

    Great video. Thanks for the content and the effort. It's really helpful!

  • @user-ip2su7gj6o
    @user-ip2su7gj6o 3 года назад

    Good video. Is there any reason why you have implemented that action via a plugin when you could do the same thing with JavaScript? It would then be instant to the user rather than taking place after create or after the record has been saved?

    • @CRMChap
      @CRMChap  3 года назад +2

      Thanks! The video aims to showcase how to develop plug-ins, as opposed to the scenario/requirement itself. However, I would disagree that JavaScript is the best route to achieving this requirement. By ensuring it is set up a server-side plug-in, you can ensure that the logic will consistently execute, regardless of how the record has been accessed (via a model-driven app, canvas app, data import etc.). By going down the JavaScript route, your logic would only ever execute at the model-driven app level. Also, synchronous plug-ins can provide that instant feedback, provided that the user saves the Dataverse row.

    • @user-ip2su7gj6o
      @user-ip2su7gj6o 3 года назад +1

      @@CRMChap thanks for your detailed reply, that all makes sense. I never said JavaScript was the best method, I was merely asking the question just because of the particular action you demonstrated. Thanks again for the informative videos.