Resolve uses a fixed set of metadata fields, while Fusion can use arbitrary. A clip in Resolves timeline doesnt transfer the metadata fields into the Fusion comp. If you enable the metadata subview in Fusion (see image 1) you can see that its empty.
Fusion has some really good ways of dealing with metadata, including SetMetadata node that lets you explicitly define your own fields. However, they cannot be used to "export"/set the metadatafields that Resolve already understands. Hence, there's no bidirectional between Fusion Page and Resolve when it comes to sharing metadata.
All expression fields in Fusion can read the metadata fields, this is useful for doing simple things like burn-ins but most importantly when it comes to CG renders you get a lot of render information baked into the image you can use for things like camera extraction.

- resolve_bug_metadata_in_fusion_page.PNG (673.13 KiB) Viewed 720 times

- resolve_bug_metadata_in_fusion_page2.PNG (695.14 KiB) Viewed 720 times
Fusion reads all the custom metadatafields in the EXR just fine, but they are not on display anywhere in Resolve other than in Fusion.

- resolve_bug_metadata_in_fusion_page3.PNG (460.85 KiB) Viewed 720 times
The request is, please consolidate the metadata handling in Resolve to be able to share freely between the pages and support custom metadata fields.
Fusion video tutorials : https://www.youtube.com/channel/UCTCeDas53OEcWcRujkQiwLg/videos?view_as=subscriber
Fusion Tools : https://github.com/statixVFX/stx_tools
Nuke 2 Fusion nodes : https://github.com/statixVFX/nuke2fusion