Forum Discussion
Ditto, this seems crazy.
- ZoeyKKhoros Alumni (Retired)
To what Peterlu said above, it would be very helpful to either be able to pull UID from the V2 API or have the bulk data api pull in the string based ID so that we're able to tie bulk data respective to where they are in the community.
- DougSKhoros Oracle
board uids are "internal" ids and differ from stage to prod, so we do not expose them via the API. the board id we do display is the string-based id that was chosen for the board when it was created.
-Doug
- lukBoss
Good point rayinala, if other Lithium "modules" like Bulk Data API etc. return data only in a specific way DougS it should be possible to also use this data with v2, otherwise we'll never get away from v1 =)...something like this should be possible:
// Bulk API will return something like this for ancestors: "/1/2/176/177/244/" // we can do "/1/2/176/177/244/"?split("/")?join(",") as preparation for the v2 query SELECT * FROM nodes WHERE uid IN(1,2,176,177,244)
I get the point that the ID's are different on stage and prod, but why does that matter? In the end we should not hardcode uids into code, especially when we know they are not the same over all instances, but that's not a reason to not expose them IMHO.
Related Content
- 5 months ago
- 10 months ago