Accounts where TOTP code should be appended (or prepended) to the password

Adding my support to this as well. I dont think this is a "special case" feature at all. I have several sites that I use daily where I find the lack of 1Password field concatenation really annoying (USAA and my OPNsense router admin page are two that immediately come to mind). Its not 1PW's fault of course, as this is a really silly hack method to not have the OTP code as a secondary input field on these login pages, but the reality is, there are sites that insist on doing it this way, and it's a real pain to not be able to auto-fill credentials this way via 1PW.

I saw a 1PW team member mention (in one of the numerous previous--and now closed--threads about this feature request) that implementing this feature poses a UX challenge, which I can understand. But it seems to me that it doesnt have to be any more complicated than having a special "dynamic password" (or something better named than that!) field type where you can construct fill-in data based on existing fields in the same vault item, using a "tag" based UI.

For example, here's how a theoretical "dynamic password" field could work, where I can build a single "dynamic" fill-in field by using concatenated "tags" that represent the names of existing fields in the vault item. This way, you could (at best) map the "password" form field entry to the "dynamic password" field for seamless auto-fills, or (at worst) manually copy and paste the contents of dynamic password field into the form. This way at the very least, you wouldnt have to manually copy and paste data from multiple fields every single time you want to login. You'd just have to copy a single field!