amplify-js: DataStore unable to work.

I ran into this issue when adding DataStore to an existing API.

Ultimately I needed to run amplify update api and follow the prompts to update the conflict resolution strategies (https://aws-amplify.github.io/docs/js/datastore#conflict-resolution) so that the API had this support and my mutations were updated to have these fields:

_version
_deleted
_lastChangedAt

I ran into this issue when adding DataStore to an existing API.

Ultimately I needed to run amplify update api and follow the prompts to update the conflict resolution strategies (https://aws-amplify.github.io/docs/js/datastore#conflict-resolution) so that the API had this support and my mutations were updated to have these fields:

_version
_deleted
_lastChangedAt

You could also add this you the transform.conf.json directly: { "Version": 5, "ResolverConfig": { "project": { "ConflictHandler": "AUTOMERGE", "ConflictDetection": "VERSION" } } }

This information must be included to the documentation! It’s pretty hard to guess… Or “@versioned” should generate it.

@rakannimer I selected optimistic concurrency per the conflict resolution docs on the DataStore page. Do that and run amplify push and it will update your mutations to include those fields.

I will also add the note here that I’ve filed an issue with being able fully use the DataStore after upgrading the API. That issue is being tracked here: https://github.com/aws-amplify/amplify-js/issues/4588

Just a warning: don’t forget to update your models when adding the Datastore, otherwise you get errors saying that version doesn’t exist (because your models need to be updated)

I skip the model update so get the error, need to run again amplify update API to take care of my models, below an example from the todolist example

You select interactively which models to update (all of them), then your schema.graphql (if you use graphql) will have all the necessary to run flawlessly

And as IssacTrvino mention: think in advance if you will use DataStore, because if you add later, you need to clean the table and reinsert all of the items again

Fixed the issue with: . Amplify update API . Enable Datastore for the whole API

Hey @kevinold

I’m getting the same error here, missing _version _deleted and _lastChangedAt.

What did you set the conflict resolution to to fix it ?

I ran into this issue when adding DataStore to an existing API. Ultimately I needed to run amplify update api and follow the prompts to update the conflict resolution strategies (https://aws-amplify.github.io/docs/js/datastore#conflict-resolution) so that the API had this support and my mutations were updated to have these fields:

_version
_deleted
_lastChangedAt

You could also add this you the transform.conf.json directly: { "Version": 5, "ResolverConfig": { "project": { "ConflictHandler": "AUTOMERGE", "ConflictDetection": "VERSION" } } }

This information must be included to the documentation! It’s pretty hard to guess… Or “@versioned” should generate it.

So once I updated via amplify-cli amplify update api , then enable DataStore for entire GraphQL , I had to remove my items from the dynamo db table and reinsert them via DataStore instead of GraphQL, the Fields were now included and ready to roll. Thanks

DataStore.save does not like to save the first record.

For me, this saves 1 record:

window.LOG_LEVEL = "DEBUG";

async function main() {
  await DataStore.save(
    new Session({
      user: `Hello`
    })
  );
  await DataStore.save(
    new Session({
      user: `Hola`
    })
  );
}

main();

Running update and adding conflict resolution did not work in may case. _version was added but not _lastChangedAt or _deleted

@undefobj I think the point missed for the case of @ykbryan was that, since this is a functional React component, it should mention that invoking DataStore should be either within a useEffect hook or as an event handler function, as the component needs to mount.

The React component lifecycle should be respected.

Thanks for the reply !

It did not work for my case, I’ll try to setup a simple repro and maybe open another issue, or I’ll stick to using vanilla GraphQL.

It sounds like you don’t have a syncable API setup. Can you do the following:

• Create react app
• Inside that directory run npx amplify-app with the schema above
• npm run amplify-modelgen inside that directory
• npm i @aws-amplify/core @aws-amplify/datastore
• npm run amplify-push
• Run your app code