SitecoreJSS deploy emptying field vales

Question

Environment:

• Sitecore 9.0 update-1
• SitecoreJSS 11.0.0

I created a sample SitecoreJSS app (using Angular), and created a new JSS component using jss scaffold <NewcomponentName>. I want to add this new component on the AppRoute page by-default (just like pageTitle).

So I added inherits: ['Route', 'NewcomponentName'], to the "routes.sitecore.ts" file and deployed to JSS app. It worked just fine, but if I filled out the data in sitecore and if I re-deploy the app again it's resetting/emptying sitecore fields.

Thanks in Advance.

Answer 1

This is expected, by default all your JSS app items will be "JSS Development Workflow". So when you deploy your App first time all items will be in "Development Mode".

So whenever you run the below/relevant commands, all your yml/yaml will overwrite respective items in Sitecore and you will loose if you made any update in Sitecore directly.

jss deploy app --includeContent
jss deploy items --includeContent

Refer the warnings in any of the item which you updated in Sitecore but not in final state of workflow, it explains.

To avoid this you may need to execute/manage workflow effectively. Check your "Review" tab, if you don't want your jss build to update item then just move it to "Content Mode" which denies access to import user and next build will not overwrite. Also if it is "Published" the content will not be overwritten because "Sitecore\JSS Import Service Users" doesn't have "Workflow State Write" access which is needed to update items when they are in a specific workflow state.

Sitecore documentation will have lot of additional details about workflow states/security and code-first approach etc.

Development Mode - Import can overwrite field values and route item layout.

Content Mode - Import user is denied item write access. Import will skip writes on the item. For route items, this means that any rendering changes or updates to datasource items are also skipped.

Answer 2

Created Sitecore ticket and they are able to reproduce my issue on their environment. But they didn't provide any fix/solution(they said they are communicating their Product Department regarding this scenario).

Temporary solution (from Sitecore):

To achieve this desired result, rather than making the default route inherit your custom components, you should create a custom route type. Custom route types will inherit the default route type automatically and can contain data fields, however unlike components these fields are shared at the route level.

Thanks - Neal