When using Media Uploader widget how do you get the objects modified by the action?
I am using the Media Uploader widget to create a Document object - once the action completes how do I get a reference to the object that it created? Normally when I run an action using other widgets I can access the objects that were created/edited.
Is there a particular pattern I should follow to have access to the object?
1 Like
We recommend using the Button Group widget to upload media in workshop rather than the Media Uploader widget: https://www.palantir.com/docs/foundry/media-sets-advanced-formats/upload-media. You can then configure the Output Object Set in the button configuration for use elsewhere in the workshop.
When other widgets runs an action, it automatically exposes,But the Media upload widget does not automatically exposes unless you explicitly store the result. This stored object/document object can be used in other widgets.
Thanks for the responses, I’ve been trying to do this using an inline form in the workshop.
I’m now getting this error
Unknown Server Error
Error: [Actions] InvalidMediaSetViewWithDatasource
Error ID: 3c9b00a8-dc53-41dc-905f-4374bcfa2ece
Related values:
knownMediaSetViews: {"ri.mio.main.media-set.893b7e7a-361f-4567-8fe1-a2fa0c522344":["ri.mio.main.view.1c0d25bd-2094-4c2e-92cb-5f94bb40a994"],"ri.mio.main.media-set.4bfa5516-3135-4a09-846f-5fff149a1214":["ri.mio.main.view.b918b206-0692-4c28-aaab-4af0aab43ca1"],"ri.mio.main.media-set.9ed9c3ab-aeba-4a83-b21b-55b47512bd61":["ri.mio.main.view.ff19c9cb-2d15-4373-9b6f-0d9b7de15d51","ri.mio.main.view.53d9ee12-1533-404d-9292-abb37c286f73"]}
mediaSetViewRid: ri.mio.main.view.7d43f1c1-8ad8-4a8c-9040-ab6cfacd7be1
mediaSetRid: ri.mio.main.media-set.9ed9c3ab-aeba-4a83-b21b-55b47512bd61
The media reference property is backed by multiple media sets. The media set I’m trying to add to is ri.mio.main.media-set.9ed9c3ab-aeba-4a83-b21b-55b47512bd61, I don’t understand why it is trying to add to the ‘wrong’ view ri.mio.main.view.7d43f1c1-8ad8-4a8c-9040-ab6cfacd7be1
I think this could have been something to do with a new feature pltr has rolled out - it seems the ontology now supports selecting a mediaset as the upload mediaset - after configuring this, the new error has gone away!
1 Like