Sitecore Unicorn standard values field child ID warnings

I thought I'd share this just in case anyone else wonders why they get the following WARN message for every single template that has a standard values set, when performing a Unicorn Sync.

To get things started:

Unicorn - 4.03 and 4.04
Sitecore - 8.2 Update 6

This happened to us when fully syncing from disk into a blank Sitecore instance, using a gulp script that calls a PowerShell sync, see below.

WARN  The standard values field of template /sitecore/templates/User Defined/Foundation/Theming/Theme/Theme Options:{XXX-XXX-XXX-XXX-XXXXXXXXXXXX} does not contain an ID that points to a child

The issue (i think) is that when unicorn de-serialises the template item, it has a field for standard values.
At the point of creation that items children haven't been created, most importantly the standard values item.
Sitecore checks the standard values field value and see that the id doesn't exist at this point, and not as a child of the item, so outputs the WARN message.
Unicorn then syncs the standard values item as a child and all is well with the data.

It just because the template item gets created before the child standard values item, if you sync again the warning is not output.
I don't think there is a way that we can resolve this as its a catch22 situation, as the template item needs to come before the standard values item in order for it to be a child, but the field needs to be populated.

Not a big issue just wanted to make sure no one else wastes any time investigating these warnings.





Comments

Post a Comment

Popular posts from this blog

Sitecore DMS and Analytics Considerations

Image
Recently I've been tasked with generating some simulated analytics traffic for our Officecore demo solution. I've been using the TrafficGenerator to do this, this is available on marketplace, but get the package from here: https://github.com/JimmieOverby/SitecoreTrafficGenerator The link on marketplace goes to an older version 0.42, 0.43 is available in the packages section. Getting the data in a has come with a few development considerations. On that basis I thought I'd discuss them and share the solutions I found. Caching: The first thing to consider is that the data you see in the engagement analytics dashboard is not real time. There are a couple of levels of caching that can make the results you see not what you expect. These levels are: Browser:  The refresh button needs to be pressed, the graphs will not auto update. The file Silverlight creates will be cached by the browser,  I found a post here,  http://sitecoreblog.alexshyba.com/2009/04/silv
Read more

Sitecore Continuous Integration DMS and the Marketing Centre

Hey all, as you know I'm a big advocate of implementing continuous integration or delivery for your Sitecore projects, in the Sitecore world much is made of the all important final step of the deployment being a Sitecore publish.  We want to get the data from the master to the web database, then we can add steps to do automated web testing such as selenium testing etc, or deploy a package to DEV, UAT, PRD. There are a few options to call a publish, you will probably have seen on many other Sitecore developers blogs,: Use a publish.aspx page that calls the publish code. Web service route, by calling Sitecore ship to initiate the publish and then call a ship endpoint and parse the response to check the late completed date to check for completion. Use Sitecore rocks powercore powersell scripts to do it. Most of the time calling the publish isn't the problem from a CI sense its knowing when its finished, my preference is the Sitecore ship approach, however we use the publis
Read more