How To Run A D365 Job In Production

แชร์
ฝัง
  • เผยแพร่เมื่อ 7 ม.ค. 2025

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

  • @italy-amanda
    @italy-amanda ปีที่แล้ว +1

    Great and easy to follow video!

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

    Thank you so much. All your videos are very helpful.

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

      Thank you so much!

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

    Nice work Peter and thanks for sharing!

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

      Thanks Alexander! I am always thrilled to see your comments. Thank you!

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

    thank you for perfect video

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

    Good video

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

    Hi Peter, great video. This will be useful in the future. I noticed the action pane interface you have looks different on what I have despite in the latest version. May I ask if there is a specific featuer for that? Thanks Peter.

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

      I will check in that. It could be Microsoft changed the way it looks in a newer version than what I have. Thanks for letting me know.

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

    Thank you for the video, I am trying to do a reception through custom script and I receive this error when I run the test : The custom script is not allowed to access the AccountingEventSourceDocumentLineLink table. any suggestion please?

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

      Make sure the D365 user that the script is running as has security roles that allow access. Also check your security policies in D365. Hope that helps.

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

    Hi Peter, I created a new vm on my laptop, and it had VS 2015, but when I jump to code, the keywords aren’t colored, and no auto intellisense, and advice please?

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

      I recommend you use VS 2019 if you are coding in X++ as that is the version supported for the current versions of D365. See if that fixes the issue.