After restore I have noticed that field "Save location" of workflow "Save as Umbraco content node" of our forms is empty. But on Development environment it is filled in.
When I open workflow "Save as Umbraco content node" I get an error "Request error: The URL returned a 404 (not found): /umbraco/backoffice/umbracoapi/entity/GetById"
When I try to submit form on local environment I get an error "System.ArgumentException: No content with that id. (Parameter 'parentId')" in log.
I found that field "RootNode" in workflow's json has id of content node from Development environment, but the same node on my local environment has different id(but the same Unique ID). After manual fix of id in database issues with "Save location" and form submitting were fixed.
Is it expected behavior of restore? Is it any way to avoid manual database fixes? Is it any way to change broken "Save location" from UI?
Workflow "Save as Umbraco content node" field "Save location"(NodeId) is broken after workspace restore
Hi
We are running Umbraco Cloud. On our Development environment we have Umbraco Forms set up. While setting up local project I restored workspace from our Development environment. I have used this documentation https://our.umbraco.com/documentation/umbraco-cloud/Deployment/Restoring-content/.
After restore I have noticed that field "Save location" of workflow "Save as Umbraco content node" of our forms is empty. But on Development environment it is filled in.
When I open workflow "Save as Umbraco content node" I get an error "Request error: The URL returned a 404 (not found): /umbraco/backoffice/umbracoapi/entity/GetById" When I try to submit form on local environment I get an error "System.ArgumentException: No content with that id. (Parameter 'parentId')" in log.
I found that field "RootNode" in workflow's json has id of content node from Development environment, but the same node on my local environment has different id(but the same Unique ID). After manual fix of id in database issues with "Save location" and form submitting were fixed.
Is it expected behavior of restore? Is it any way to avoid manual database fixes? Is it any way to change broken "Save location" from UI?
Thanks,
Kostiantyn
is working on a reply...