Skip to main content

I have a file where I’m trying to add metadata using a template we have been using in the past.
When I try to save the metadata using the UI (when editing the file) I get back the following error:
"An error has occurred while updating metadata. Please refresh the page and try again."

I’ve tried refreshing the page and repeating the process, but still get the same error.
When I happen to look at the Chrome Dev Tool Console window I can see that the Box UI is getting an error response back from an ajax call they posting. The error says:
{
"message": "Encountered invalid value for template field key=alfrescoCreatedDate with id=eb….",
"code": "bad_request",
"request_id": "d…."
}
This is a hidden field we have had for several years and never ran into any issue trying to save the metadata. It really shouldn’t be trying to do anything with this hidden field.
Have any of you run into this? Is there any work around?
Support so far has not been helpful.

👋 Hi ​@Greg Mercer, welcome to the Box Community! Thank you for bringing this issue to our attention.

 

Upon further investigation, we’ve identified a known issue related to saving metadata. The problem is observed when there are multiple metadata fields and some are left unselected or blank. We apologize for any inconvenience this may have caused.


Our engineering team is actively working on a fix and we hope to have it resolved as soon as possible.


As a temporary workaround, you can try setting all the metadata fields once, and subsequently remove the unwanted values. This may help bypass the issue.


We’ll keep you updated here as soon as we hear back from our internal team. You may also follow up on the ticket you’ve submitted to our Product Support.

 

Thank you for your patience, and please don’t hesitate to reach out if you have any further questions or concerns. 😊

Hmm… I would need to make all the hidden fields visible in the metadata template. 
Do you feel that it would be safe to move these fields from hidden to visible and then later back to invisible?

Dear Greg, thank you for your response. I'm currently following up with our internal team to confirm that, and I’m still waiting on their update. Sorry for the delay.


Also, please rest assured that this is a high priority for us, and we’re working diligently to resolve the issue.


I’m closely monitoring the investigation and will keep you informed. I’ll be sure to let you know as soon as we have a resolution. 🙌

Hello ​@Greg Mercer, thank you for your patience!

 

Our engineering team has identified that this issue is related to a regression in production, and the recent change appears to have caused it.


The fix was deployed around 5 PM PST yesterday, so the metadata fields should now be functioning as expected. Could you please try again and let us know if you encounter any further issues?

 

Thanks again, and have a wonderful day! 😊

Reply


Terms & ConditionsCookie settings