Bug with amplify generated composite keys

Hello, I created a composite sort key using the amplify cli. The composite key includes the a person’s first and last name. Most of the time the composite key is generated correctly in Dynamo DB like: john#doe. However, sometimes it’ll be saved as ${ctx.args.input.first}#${ctx.args.input.last}. Subsequently, when I try to run a query with this composite key, it skips over the records that have this faulty composite key. I have not messed with any of the code auto generated by amplify and have confirmed that the first and last name values due indeed exist in the data row. Also, the primary keys were also defined. If anyone can point me in the right direction that would be great!

[paulsson]

@attilah @kaustavghosh06 @SwaySway @yuth @ammarkarachi @edwardfoyle @litwicki this is such a critical bug it should be at the highest priority of any work for Amplify CLI. This essentially makes accessing DynamoDB data that uses a composite sort key completely unreliable and inconsistent because a record “disappears” (is not returned) if an update is performed that does not include the fields that make up the composite sort key. This can cause customers to think their data just disappeared… how can anything be more critical to fix than that? This has already been well diagnosed. Can the Amplify community please have an update when this will be fixed?

[jdonboch]

any updates? still a bug after being identified over a year ago (v.4.49.0)