Hi there !
I’ve created a new object type, waited for the indexing to finish up and then decided to created a new custom object view.
When I open the Object View Tab and make a quick edit, I notice that the “Save and publish” button I’m used to seeing only says “save” and is grayed out: impossible to save anything.
Having a look at my console logs, I see a series of errors such as:
foundry.objects.workshop.app.deserializeParamValue: Failed to deserialize param value for objectSetRid: packageName=@foundry/workshop-core Error: {“type”:“STATUS”,“status”:422,“body”:{“errorCode”:“INVALID_ARGUMENT”,“errorName”:“Conjure:UnprocessableEntity”,“errorInstanceId”:“53e56123-79a8-4571-9215-175dd1f845ba”,“parameters”:{}}}: packageName=@foundry/workshop-core
and
Failed to deserialize param value for objectSetRid {entityName: 'foundry-frontend', entityVersion: '6.440.22', safeParams: {…}, unsafeParams: {…}}entityName: "foundry-frontend"entityVersion: "6.440.22"safeParams: {packageName: '@foundry/workshop-core', bundleName: 'workshop-app'}unsafeParams: {throwable_message: '{"type":"STATUS","status":422,"body":{"errorCode":…ameters":{}}}: packageName=@foundry/workshop-core'}[[Prototype]]: Object
Error: {throwable_message}
at https://{hostname}/assets/content-addressable-storage/frontend/34396ba8e4c0036004fb13bdfdddab2371faf6ad2dbc7e3b092539d7a5d88a52.js:2:243430
at o (34396ba8e4c0036004fb13bdfdddab2371faf6ad2dbc7e3b092539d7a5d88a52.js:2:247888)
at a (34396ba8e4c0036004fb13bdfdddab2371faf6ad2dbc7e3b092539d7a5d88a52.js:2:243421)
at errorImpl.Object.assign [as errorImpl] (34396ba8e4c0036004fb13bdfdddab2371faf6ad2dbc7e3b092539d7a5d88a52.js:2:244425)
at Object.objectSetRid (34396ba8e4c0036004fb13bdfdddab2371faf6ad2dbc7e3b092539d7a5d88a52.js:3:1098969)
at async https://{hostname}/assets/content-addressable-storage/frontend/34396ba8e4c0036004fb13bdfdddab2371faf6ad2dbc7e3b092539d7a5d88a52.js:3:1101151
at async Promise.all (index 0)
at async AC (34396ba8e4c0036004fb13bdfdddab2371faf6ad2dbc7e3b092539d7a5d88a52.js:3:1100891)
at async AP (34396ba8e4c0036004fb13bdfdddab2371faf6ad2dbc7e3b092539d7a5d88a52.js:3:1101429)
at async Promise.all (index 0)
Any idea what might be going on ?
I’m able to save and publish other object views that had been created previously but as of this morning I am not able to save any new one - I tried creating 2 different objects, both resulting in the same outcome.
Thanks !
Hey,
Were you able to try saving your edits after the first indexing job completed?
Additionally, if you’re seeing Save that means auto-publish is turned off which is sometimes (maybe usually?) the case for brand new Workshop modules (Object Views are really just Workshop modules). If the Save or even the Save and publish button is grayed out, it means Workshop hasn’t detected any net new changes to the application’s config since the last saved version.
To turn on auto-publish, look to the top-left corner of the page just under the bold text that represents the Workshop module’s filename/title. You should see a clickable blue text representing the module’s version number. When you click on it, there should be a modal that pops up in the middle of the page which shows version history; at the top of the modal is a toggle that controls auto publishing.
Hey Josh,
auto publish should be turned on, as I can see a “Autosaved at 3:02 PM” message. Making changes in the Workshop doesn’t result in turning the Save button ungray unfortunately, yet changes are being recognized since when I make some I see the option saying “Discard autosaved draft and reload the module? This action cannot be undone.” and I’m able to discard my draft.
Comparing this object view with any other, they seem to have the same configs and the same permissions, the main difference being that the broken one reports a bunch of errors in my developer tools console.
I’m also seeing this kind of error:
Uncaught (in promise) ApolloError: Error encountered while executing ...
LatestObjectViewVersionQuery Error: Error encountered while executing ...
Hey,
Autosaved is different from published; if you see a light grey Unpublished tag in that area of the page, that means the version of the module you’re currently seeing in Edit Mode is not yet available to the Object View and anyone that is viewing it.
This does seem to be an odd error in the backend if it’s mentioning Apollo (it’s the service that handles change management for Gotham and Foundry instances), so I’m afraid I’m not too sure how to handle that without more information.
If you’re able to recreate the Object Type after deleting the current one (assuming this Object Type isn’t already being used in production workflows), that may give you a fresh clean slate without encountering the same errors.
I think I’m suffering from the same issue.
Unable to save an Object View from a new OT I created today. I have Ontology Owner perms for the OT and Control Panel → Org Perms → Object View Editor perms. I’m also an Owner on the datasource project.
Yep, I’m familiar with Apollo, I worked at Palantir for 8 years 
sadly now that I’m on the other side I don’t have such an easy access to the support team.
I did indeed try to recreate my object - deleted it and created a new one - but I got the same outcome, which at least shows that it’s a reproducible bug.
Hopefully someone on the support team will see this message and might be able to help out, although I wouldn’t be surprised if this has already been identified internally and a fix might come out in a few days.
Hi, we’ve identified the issue and have pushed out a fix - object views should save as expected again. Thank you for flagging this, let us know if you encounter any other issues or have further questions!