Nested Relational Data Not Returned in GraphQL API Queries on AWS Amplify about amplify-js HOT 5 CLOSED

Hi @chrisbonifacio, it return the same result with basicinfos null, i need to use it for my app at least optimistic or merge conflict resolution.
Thanks !

from amplify-js.

Hi @Glognus thank you for the update.

Unfortunately I haven't been able to reproduce this issue.

I tried with the following schema

# This "input" configures a global authorization rule to enable public access to
# all models in this schema. Learn more about authorization rules here: https://docs.amplify.aws/cli/graphql/authorization-rules
input AMPLIFY {
  globalAuthRule: AuthRule = { allow: public }
} # FOR TESTING ONLY!
type User @model @auth(rules: [{ allow: private }, { allow: owner }]) {
  id: ID!
  name: String!
  basicInfos: BasicInfos @hasOne
}

enum Gender {
  MALE
  FEMALE
}

type BasicInfos @model @auth(rules: [{ allow: private }, { allow: owner }]) {
  id: ID!
  gender: Gender
}

I created a BasicInfo record, then a User with a basicInfoId to make the relationship.
I received both the User record and BasicInfo nested data on mutation

I then tried the same GetUser query and received the same response with nested data.

Can you share how you are creating the records? Are you making sure to include a _version in the mutation arguments when creating a User? This is required for DataStore-enabled APIs (conflict detection enabled) and not including the version can result in no update to the record.

If you are creating a user first, then a BasicInfo, and finally updating a User with the basicInfoId, this might explain why disabling conflict detection results in updates seeming to work normally and able to retrieve the updated User record.

But to be sure, we'd have to see how you are trying to establish the connection between the records.

from amplify-js.

I've discovered a potential lead on the issue, It appears to be related to conflict resolution settings. Disabling conflict resolution on my API allows the nested relational data to be correctly fetched.

This suggests a potential bug or interoperability issue between AWS Amplify DataStore and AWS Amplify API when conflict resolution is enabled. It seems to interfere with fetching and returning nested relational data.

Is there a workaround or a fix planned for this issue? Any guidance would be appreciated.

from amplify-js.

Hi @Glognus thanks for raising this issue and providing detailed repro steps! Can you try running the same query in the AppSync console with conflict resolution enabled? This will help rule out whether the DataStore client is the source of the issue.

We'll try to reproduce this internally with the steps given and provide an update soon.

Also, inconsequential to the issue, but were you using conflict detection/resolution purposely? Or do you not need it in your application?

from amplify-js.

Hi 👋 Closing this as we have not heard back from you. If you are still experiencing this issue and in need of assistance, please feel free to comment and provide us with any information previously requested by our team members so we can re-open this issue and be better able to assist you.

Thank you!

from amplify-js.