I am familiar with the 'Propagate data to versions' command in the version menu for a master, but what does the 'Propagate' command on the same menu for a version do? I had thought is was the same as a 'Propagate data from a master' command but that doesn't seem to be the case.
Does the same.
Does the same as what? Do you mean the 'Propagate' command in a version propagates to versions of the version? Like in a version chain? Wouldn't that make the version also a master (with the original 'Propagate data to versions' command) ?
No. It determines the master(s) of the selected version(s) and then initiates a propagation from these masters to all their versions.
That is how I had originally interpreted it, but it doesn't seem to work for me. I've tried several times, making sure that the master data had been written back, etc.
Would a log help, or do you need something else?
From looking at the code I would say it works as intended. The masters are searched, then propagation is performed.
I recommend you open a bug report and add a debug log file from a session where you used that command. Also do a check if the versions find their masters (e.g. using the variable in he var toy app). I'm currently totally busy with other things and this is a rather obscure and potentially time-consuming case. Put it into a bug report and I will look into this for one of the next releases.
PS.: I've just tested this and it works here. Even for manual version relations.