P: Lens metadata field missing on import

Thank you, I will give that a try 🙂

Thank you, I will give that a try 🙂

Thank you Simon.

Here are my recommendation to recover the missing lens metadata once you get the next update:
1. In the library module, filter and find all the photos that you imported into Lr since the Lr 6.5 release.
2. Select them all (Ctrl/CMD+A)
3. Invoke Metadata>Save Metadata to Files menu command to save the latest metadata (that includes the latest develop settings) to the files.
4. Invoke Metadata>Read Metadata from Files menu command to read the latest metadata back, including the missing lens metadata.

John - that sounds as though it could be useful but you mention saving metadata back to the file whereas I and others would want to retain the develop settings when re-importing.
Please could you clarify.
Thanks

@lhiapgpeonk The way to prevent this problem is simple - first save the metadata back to the files. That's Ctrl S on Windows and Cmd S on Mac.

Will there be a possibility to re-import just the lens metadata? Re-importing metadata usually reeks havoc with development settings (read: voids them) and I want to avoid that.

Unfortunately I cannot comment on the exact timing of the dot release update, but it should happen fairly quickly, in the next week or two.

Apologies for the double post; apparently I can't delete it.

In other words, the official Adobe response is "we don't plan on fixing this issue until the next major dot release." If someone from Adobe had posted this in response to my original post a month ago, this would have been a disappointing, but at least honest and understandable statement given the underlying business and software development factors. It also would have allowed customers to decide for themselves whether this was an acceptable delay given their current needs, and whether rolling back was an acceptable workaround for them. But that didn't happen. Instead, we got the full story only after one month and a few vague "we're working on it, stay tuned" promises in the interim. I'm not at all surprised that this is how it unfolded, but I don't appreciate the lack of transparency.

At the moment, I'm willing to put up with the workaround and (begrudgingly) continue to pay for CC, because the older DNG converter still works with my existing gear. But I have a hard stop: I doubt the workaround will work for the D500 that I plan on upgrading to. I hope the fix is out by the time I get one, otherwise that could be enough to make me migrate off of Adobe software.