I was already interested in snapshot debugging and this was something I still had to research. Thanks for sharing youw knowledge and experience. As always great video, great explanation and great examples! Keep up the good work Erik!
The BIGGEST problem, if I understood correctly, is that this is only for our session, usually errors occur on users sessions. Isn't there a way to force that debuggingcontext with the users session guid?
That is correct. Refresh in the browser will not create a new session, and you have specified the next session in your configuration. Maybe you could have attached to the client's session id in your snapshot configuration. That is a better way to repeat snapshot sessions for the same client. On the zip content, they are serialized stack frames.
Table of contents - first part
1:30 Snapshot
2:49 - D365 Snapshot debug permission group(permission set)
3:59 - Definition of snapshop
5:08 - Record example
5:49 -- What is exactly recorded
6:08 -- Breakpoints/snappoints
7:30 -- Launch.json
08:40 -- Initilizae Snapshot
10:30 -- Stop recording
11:53 -- Replay example
15:05 Profiler
I was already interested in snapshot debugging and this was something I still had to research. Thanks for sharing youw knowledge and experience. As always great video, great explanation and great examples! Keep up the good work Erik!
Thank you for this, really useful info
Love youre videos! Thanks a lot 👌
Not sure why they thought having only a guid is smart for filenames
The BIGGEST problem, if I understood correctly, is that this is only for our session, usually errors occur on users sessions.
Isn't there a way to force that debuggingcontext with the users session guid?
Yes, you can specify a specific session instead of the way I did it.
@@Hougaard How?
Bonus content!
Great Ekik.
As far as I know, you need to have the very same symbols as in the production environment.
How do you download these symbols?
Ta.
Great question, you can download symbols from a production environment using the snapshot configuration
I think that you need to start a new session by using a new tab in your browser. Otherwise it will take the same session.
Could be, but that just shows how finicky the procedure is...
That is correct. Refresh in the browser will not create a new session, and you have specified the next session in your configuration. Maybe you could have attached to the client's session id in your snapshot configuration. That is a better way to repeat snapshot sessions for the same client. On the zip content, they are serialized stack frames.
@@kalmanberes828 Thanks Kalman, I'll try that :)