Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

馃悰 Bug: API V2 Update API /rowid is missing #7021

Closed
1 task done
emre1e opened this issue Nov 17, 2023 · 6 comments
Closed
1 task done

馃悰 Bug: API V2 Update API /rowid is missing #7021

emre1e opened this issue Nov 17, 2023 · 6 comments
Assignees

Comments

@emre1e
Copy link

emre1e commented Nov 17, 2023

Please confirm if bug report does NOT exists already ?

  • I confirm there is no existing issue for this

Steps to reproduce ?

Update to 202.7

Update API doesnt work, because its not accepting the row id.

image

Desired Behavior

It should accept it.

image

Project Details

Node: v18.17.1
Arch: x64
Platform: linux
Docker: true
RootDB: pg
PackageVersion: 0.202.7

Attachments

No response

@dstala
Copy link
Member

dstala commented Nov 17, 2023

@emre1e in v2, we have unified single & bulk API. Record ID hence should be part of body of the message.
Details here. https://data-apis-v2.nocodb.com/#tag/Table-Records/operation/db-data-table-row-update

@dstala dstala assigned dstala and unassigned o1lab Nov 17, 2023
@dstala dstala added this to the v0.203.0 milestone Nov 17, 2023
@emre1e
Copy link
Author

emre1e commented Nov 17, 2023

Somehow its still not working:

{
"Id": 2821,
"Aktenzeichen_eagle": "GAM2399999",
"Verfahrensstatus": "Vergleich"
}

Return:

{
"msg": "Record with pk undefined not found"
}

@pranavxc
Copy link
Member

pranavxc commented Nov 17, 2023

@emre1e Can you try the following image, earlier today we fixed some issue regarding id extraction.

docker run -d -p 8888:8080 nocodb/nocodb-timely:0.202.7-pr-7017-20231117-1015

@emre1e
Copy link
Author

emre1e commented Nov 17, 2023

its still the same

image

@pranavxc
Copy link
Member

its still the same

image

Thanks for the quick reply and I've few queries which will help us to debug.

  1. Are you using composite primary key ?
  2. Is it external database ?
  3. Can you try passing "id"(which is the actual column name) and test once.

@emre1e
Copy link
Author

emre1e commented Nov 17, 2023

no only id is primary key
no docker internal postgres
tried id but same

@emre1e emre1e closed this as completed Nov 17, 2023
@dstala dstala removed this from the vFeature milestone Dec 29, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants