+1Hi
Can someone help, how I can identify the collection id (number) used in DATA API, using the collectionId get from documentContents RESTAPI.
Thanks.
Best answer by Michael B
I looked to see if there was a reasonably small path to add both IDs to the `/content` endpoint, but unfortunately there is not. There are good reasons we moved away from the ID field, which doesn’t scale to the complexity of data that we have today. With a relatively simple example, it is 1:1 but more complex documents can’t deterministically make that connection.
+4Hello Psuresh, I am reviewing your question now and will have a response soon.
+4Unfortunately, I can’t find a deterministic way to connect them either. Our Data APis are considered “legacy” products that are not being actively updated as changes are made. The “id” they take is actually an auto-incrementing ID which effectively just points at the actual id of the collection. The content endpoint provides that actual value.
Remaking the Data endpoints to fit our modern APIs is a feature that has been requested before, and I put in a new request to consider it for prioritization. However, it is not currently on our roadmap.
+1Unfortunately, I can’t find a deterministic way to connect them either. Our Data APis are considered “legacy” products that are not being actively updated as changes are made. The “id” they take is actually an auto-incrementing ID which effectively just points at the actual id of the collection. The content endpoint provides that actual value.
Remaking the Data endpoints to fit our modern APIs is a feature that has been requested before, and I put in a new request to consider it for prioritization. However, it is not currently on our roadmap.
Hi Michael, thanks for your response… it would have been great if we can get a work around/ patch release from product team to solve this mapping between Lucid Chart API and Data API.
+4I looked to see if there was a reasonably small path to add both IDs to the `/content` endpoint, but unfortunately there is not. There are good reasons we moved away from the ID field, which doesn’t scale to the complexity of data that we have today. With a relatively simple example, it is 1:1 but more complex documents can’t deterministically make that connection.
A Lucid account is required to interact with the Community, and your participation is subject to the Supplemental Lucid Community Terms. You may not participate in the Community if you are under age 18. You will be redirected to the Lucid app to log in.
A Lucid account is required to interact with the Community, and your participation is subject to the Supplemental Lucid Community Terms. You may not participate in the Community if you are under age 18. You will be redirected to the Lucid app to log in.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
