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.
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?
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.
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?
Great and easy to follow video!
Thank you so much. All your videos are very helpful.
Thank you so much!
Nice work Peter and thanks for sharing!
Thanks Alexander! I am always thrilled to see your comments. Thank you!
thank you for perfect video
Good video
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.
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.
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?
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.
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?
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.