Embedded python code suddenly gone

Question

This happens with some regularity. The embedded script in a python script tool gets replaced by the filepath to to the temp *.py file for the code. I am refraining from using embedding scripts for now because of this but if anyone knows why this is happening, I would be most grateful. It is handy to use embedded scripts. Thank you,

Randy McGregor

RandyMcGregor_BMcD · Answer

I have completely given up on embedded code. I always create a *.py script and load it into the tool. Works fine.

CarsonMorton · Answer

This just happened to me too. I've had it open in visual studio code for weeks and would tinker with it every now and again. I had noticed that the name of my script had changed to some odd name like setmw2bu or something. Then today VSC was blank except for a message about the file not existing.

So, starting from scratch, I have created a .py from VSC instead of Pro. Is that going to keep it safe? Can I run the code in Pro? (I don't see it in the catalog view)

RandyMcGregor_BMcD · Answer

Thanks for the information, but sorry this happened to you. I just gave up on embedded code. This is a VERY weird one. Overall, working with python code in ArcPro has been quite unstable compared to ArcMap. Editing validation code is cumbersome as well. When you open the temp. validation script and edit it and save, you have to close it down and reopen to make more changes as they don't register after the first save.