ID 504611 - Entering %V in the Write nodes file name stops the Write node from passing through any metadata information with the read file option enabled

Follow
  1. The Foundry SANDBOX
  2. Bug Tracker
  3. Nuke

Problem summary
When entering the %V in the Write nodes file name, it stops the Write node from passing through any metadata information with the read file option enabled.
 
Customer reported version
Nuke 12.2v9
 
Customer reported platform
CentOS7
 
Steps to reproduce
 
1) Open the attached script, the script has a Colorwheel node using input A and a Checkerboard node using input B of a Merge node, the merge is then plugged into a ModifyMetaData node with a set action added, the key is set to test and value is set to foobar, the ModifyMetaData node is plugged into two separate Write nodes that are being viewed by a Viewer node.
 
2) Open the Write1 and Write3 nodes property windows and press the Render button in both of the Write nodes and then click OK in the popup window.

2) Create a new Script Editor window by Right-Clicking on the Properties tab, Browsing to Windows, and then select Script Editor.

3) Enter the code  nuke.toNode("Write1").metadata() into the Script Editor window and press CTRL+Enter to run the code, this should display the Metadata correctly.
 
4) Enter the code  nuke.toNode("Write3").metadata() into the Script Editor window and press CTRL+Enter to run the code, this should display no Metadata as the file name has a %V added to it.
 
Expected behaviour
For the Metadata to display if you are using the %V to view the formatting key.
 
Actual behaviour
If you add a %V to a file name and write this out it will cause the metadata to not pass through the write node when the read file option is enabled.
 
Workaround
Unknown.
 
Reproduced by support
This bug has been reproduced in:
Nuke 13.1v3 - Windows 10 - macOS 10.15.3 - CentOS7
Nuke 13.1v1 - Windows 10
Nuke 12.2v10 - Windows 10 
Nuke 12.0v1 - Windows 10
Nuke 11.1v3 - Windows 10 - macOS 10.15.3 - CentOS7
 
Unable to reproduce bug in:
Nuke 11.1v2 - Windows 10 - macOS 10.15.3 - CentOS7 - Regression
 
Earliest version tested
Nuke 11.1v2 - This issue doesn't appear in this version and has regressed
 
 

    We're sorry to hear that

    Please tell us why