val(newid) .
}
}
}
```
The above upsert mutation works but the xid is never set which I assume means it’s empty when executing the mutation block. How do I get my newid value into the mutation block where I need it?
The first query which returns my users seems to suggest the value only exists in the context of a specific node since the newid value isn’t shown on the “Chris” node which is why it seems to be empty during my mutation.
---
### Author:  [@amanmangal](https://discuss.dgraph.io/u/amanmangal)
#### Post date: [January 27, 2020, 11:57am UTC](https://discuss.dgraph.io/t/using-an-upsert-block-to-increment-an-id/5889/2 "2020-01-27T11:57:51Z")
I think relying on sorting of UIDs to get the latest inserted user would be a bad approach. We assign UIDs in batches and a later inserted user could potentially have lower UID. A better approach may be to keep a separate predicate and store the latest ingested XID there, like a counter and use that instead. This can have some negative impact on performance, though, happy to explain more if you have any question with the approach.
---
### Author:  [@Fantastitech](https://discuss.dgraph.io/u/Fantastitech)
#### Post date: [January 27, 2020, 3:42pm UTC](https://discuss.dgraph.io/t/using-an-upsert-block-to-increment-an-id/5889/3 "2020-01-27T15:42:33Z")
I’m not relying on the UIDs. That’s just an example from the linked post. I’m actually using `orderdesc: xid, first:1` to get the last saved xid. My problem is the variable not being recognized in the mutation block which wouldn’t be solved by changing how it’s stored.
---
### Author:  [@amanmangal](https://discuss.dgraph.io/u/amanmangal)
#### Post date: [January 28, 2020, 8:07am UTC](https://discuss.dgraph.io/t/using-an-upsert-block-to-increment-an-id/5889/4 "2020-01-28T08:07:42Z")
Will you share the actual query? In the above query, I see you are using `first:-1` which I thought could be problametic.
---
### Author:  [@Fantastitech](https://discuss.dgraph.io/u/Fantastitech)
#### Post date: [February 2, 2020, 3:51am UTC](https://discuss.dgraph.io/t/using-an-upsert-block-to-increment-an-id/5889/5 "2020-02-02T03:51:24Z")
```auto
upsert {
query {
var(func: type(User), orderdesc: xid, first:1) {
lastid as xid
newid as math(lastid + 1)
}}
mutation {
set {
_:user "User" .
_:user "Matt" .
_:user "None" .
_:user "matt@example.com" .
_:user "password" .
_:user val(newid) .
}
}
}
```
---
### Author:  [@amanmangal](https://discuss.dgraph.io/u/amanmangal)
#### Post date: [February 12, 2020, 6:12am UTC](https://discuss.dgraph.io/t/using-an-upsert-block-to-increment-an-id/5889/6 "2020-02-12T06:12:27Z")
This seems like a bug similar to already raised on GitHub here [Bug with multi-level Upsert Block · Issue #4692 · dgraph-io/dgraph · GitHub](https://github.com/dgraph-io/dgraph/issues/4692). I am looking into this issue. The problem is the line `_:user val(newid) .`. I will post more updates soon. Thanks
---
### Author:  [@amanmangal](https://discuss.dgraph.io/u/amanmangal)
#### Post date: [February 12, 2020, 9:34am UTC](https://discuss.dgraph.io/t/using-an-upsert-block-to-increment-an-id/5889/7 "2020-02-12T09:34:10Z")
This is a similar bug, and we will fix it as soon as we can. I have posted an example on the GitHub issue [Bug with multi-level Upsert Block · Issue #4692 · dgraph-io/dgraph · GitHub](https://github.com/dgraph-io/dgraph/issues/4692).
---
### Author:  [@amanmangal](https://discuss.dgraph.io/u/amanmangal)
#### Post date: [February 12, 2020, 4:15pm UTC](https://discuss.dgraph.io/t/using-an-upsert-block-to-increment-an-id/5889/8 "2020-02-12T16:15:22Z")
@MichelDiz pointed out that there is a separate GitHub issue that tracks this issue [It is not possible to create a new node from another using Upsert Block · Issue #4712 · dgraph-io/dgraph · GitHub](https://github.com/dgraph-io/dgraph/issues/4712).
---
### Author:  [@system](https://discuss.dgraph.io/u/system)
#### Post date: [March 13, 2020, 4:19pm UTC](https://discuss.dgraph.io/t/using-an-upsert-block-to-increment-an-id/5889/9 "2020-03-13T16:19:55Z")
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.