Forum Discussion

rayinala's avatar
rayinala
Mentor
8 years ago

How to get the boardId with board uid in v2 API calls

Hi

 

Is there any v2 api call to get the board id with board uid in LIQL Query.

 

Thanks,

Ramesh.

  • peterlu's avatar
    peterlu
    Champion
    5 years ago

    DougS  Another 2 clients are asking to include UID in the apiv2 call for  "nodes" collection today. Or please change the LSI tool to use the normal string based ID.

  • ZoeyK's avatar
    ZoeyK
    Khoros Alumni (Retired)
    4 years ago

    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. 

  • DougS's avatar
    DougS
    Khoros Oracle
    8 years ago

    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

    • rayinala's avatar
      rayinala
      Mentor
      8 years ago

      Hi DougS,

       

       

      The response of Bulk Data API contains the board.uid not the actual boardId. So if we want to pull the full details of Board, we see fetching with boardId is the only way in v2API. Could you please guide us how we can solve this issue?

       

      Thanks,

      Ramesh

       

      • luk's avatar
        luk
        Boss
        7 years ago

        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.