Hui Zhao

Hello @Rayv1 thanks for inquiring and providing detailed example of your use case. **About the db managed `createdAt` and `updatedAt` fields** Currently amplify-flutter models should contain `createdAt` and `updatedAt` already...

Hi @Rayv1 we will keep this issue open for the purpose of tracking this feature request. Thanks.

Hi @PeblTech I'm a bit lost with your comment >Without the default createdAt and updatedAt fields being added to the Model As I mentioned above, `createdAt` and `updatedAt` are default...

Hi @surisakc can you paste the generated Dart class files for `Building2` and `Building3`?

Hello @surisakc sorry for the delayed response. I did some digging, looking at your schema: `ownerField: "users"`, you are trying to use the dynamic group authorization. ```graphql type Building2 @model...

Hi @surisakc , for this auth rule `{allow: owner, identityClaim: "sub::username", ownerField: "users"}` (owner field is a list), as the document states, it also doesn't support AppSync realtime subscription, I'd...

Hi @surisakc >Is it possible if I set the owner field to a family ID (to share a model in a family with many users) using the lambda function while...

The process you described makes sense to me. > When UserA doesn't want to share the model anymore that the Cognito API can set null or empty value to the...

Hi @surisakc looking at the resolver, it listed fields in the model schema as ``` ["id","name","status","data","familyId","_version","_deleted","_lastChangedAt"] ``` Which indicates your model should have `familyId` field instead of `owner`... Does this...

>By setting {allow: owner, identityClaim: "custom:familyId"}, is it by default using the accessToken for access authorization or will it use idtoken which has identity claim in it (I saw my...