I want to generate URL links to Object views for all the Objects of a given Object Type. In order to do this, my understanding is that I need to have the RID for the Object for which I want to generate the link.
The Object Type I want to retrieve does not have a Property that contains the RID and I am unsure how I can get an export of all the Objects in my Object Type with the RID included as a column in the exported data. Is there a way I can achieve this in e.g. Contour or a Code Workbook?
Also open to other strategies, such as if there is a way to include the RID as a Property of the Object Type.
You can have an automation, that every time you have a new object, you run an action that fills a string property name with the rid details, for example object_rid = this_is_your_object.rid.
Other option I came to learn recently is:
Create a workshop module
Inside this workshop Module +Add a Widget that is an object view.
And then you just have to add to the end of your link: https://.com//workspace/module/view/latest/<link_to_your_workshop_main_module>?variable=<your_special_id>
Where are you trying to create the export / generate the URL links?
If you are doing this in a code workbook, the public api for searching objects should return to you the RIDs for all objects in the set. I’d recommend generating an OSDK to make this query easier
I think I see what you are going for with this, and thank you for your explanation.
What I am going with is instead using the primary key id to do what I believe your step 6 is doing.
I initially thought I could only pass RIDs as parameters in my URL construction, but the docs on generating URLs show how to use the primary key id instead.
I initially was trying a Code Workbook, but ultimately found a better way to accomplish what I needed. I was not aware I didn’t actually need the RID to generate the Object explorer link, but could accomplish this with the primary key id for my Object Type.
So, my issue is resolved, however I do have an outstanding concern about bulk export of Foundry’s internal resource identifiers. It’s unclear to me if resource identifiers are hidden from table views as a default (in e.g. Contour or Code Workbook), or if that’s just not expected for developers to need resource identifiers in bulk, so they are never exposed. That may not ever come up though, given you can query via the primary key id, which is easy to get a bulk export for in my case.
