Amplify Studio Data Manager does not sync data to DynamoDB

[danielcastellanosT]

Recently I updated my schema model and start using graphql transformer v2 syntax. But I have experienced problems creating/updating data. This happens specifically with data models that have relationships.

Is this related on how I defined the model relationships? Here's exactly how it's written:

  id: ID!
  campaign_developer: CampaignDeveloper! @belongsTo
  name: String!
  thumbnail: String!
  city: String!
  address: String!
  zone: String!
  latitude: Float!
  longitude: Float!
  campaign_opening_date: AWSDate!
  campaign_closing_date: AWSDate!
  state: CAMPAIGN_STATE!
  documents: [String]
  financial: CampaignFinancialInfo @hasOne
  marketing: CampaignMarketingInfo @hasOne
  investments: [Investment] @hasMany
  cancellations: [Cancellation] @hasMany
}

type CampaignFinancialInfo @model @auth(rules: [{ allow: public }]) {
  id: ID!
  campaign: Campaign! @belongsTo
  annual_yield_rate: Float!
  funding_goal: Float!
  funding_committed: Float!
  funding_raised: Float!
  campaign_type: CAMPAIGN_TYPE!
  campaign_class: CAMPAIGN_CLASS!
  minimum_funding_required: Float!
  term_in_months: Float!
  warranty: String!
  repayment_frequency: PAYMENT_FREQUENCY!
  grace_period_in_months: Float!
  interest_grace_period: Boolean!
}

For example when I try to connect a Campaign object to a CampaignFinancialInfo object through Content Manager, one of the next 2 scenarios can happen:
Content Manager updates the data succesfully. But won't sync it on DynamoDB.
Content Manager aparently "updates" the data succesfully. But when I read the data, it is in the previous state. And of course, won't sync on DynamoDB.
When updating a relationship, the relationship id property is the same id of the record instead of the id of the related record in the related table.

[cwoolum]

Are you seeing any errors in the Chrome debugger? Can you provide your app id and region?

[arundna]

Closing the issue due to inactivity - This repository only accepts new feature requests for AWS Amplify Studio. For technical support, we encourage you to open a case with AWS technical support if you have AWS support plan. If you do not have an active AWS support plan, we encourage you to leverage our Amplify community Discord server where community members and staff try to help each other with Amplify.

[github-actions]

⚠️COMMENT VISIBILITY WARNING⚠️

Comments on closed issues are hard for our team to see.
If you need more assistance, please open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.