This article describes the known issues with the Sitecore® Experience Platform™ 9.0.
For all Sitecore Experience Platform documentation, please visit the Sitecore Documentation Site.
For information about the availability of the fixes for the mentioned known issues, please refer to the Release Notes of the future Sitecore Experience Platform releases.
- [Fixed in XP 9.0 Update-2] When Azure Search performs a search query that contains a hyphen for items that are filtered by language, it returns the item for all languages. (171546)
- You cannot segment by email behavior when you use the Azure Search provider. (170500)
- When you upgrade from XP 9.0 Initial Release to 9.0 Update-1, we recommend that you rebuild the index (although it is not essential).
If you do not rebuild the index, either by choice or because you use Azure Search, EXM might report an incorrect number of recipients due to changes that were made to the EmailAddressList facet. This does not affect the number of sent email messages, but it will impact A/B testing on messages.
This is only a problem for existing contacts that you have created in XP 9.0 Initial Release. The issue is resolved when the contact is indexed again or the index is rebuilt. (197114)
- [Fixed in XP 9.0 Update-1] The Personalization dialog does not show data when Sitecore is set up in mixed mode. Mixed mode is when the Processing server is deployed in the Cloud and the Content Management server is deployed on the premises. This error occurs because in mixed mode, the Processing and CM servers use different Master databases. (186028)
- In the Experience Profile, you can only search for an exact name or email address. You cannot search for part of the name or email address. (160701)
- If you have disabled the PII compliance setting, you can only search by name or email address in the Experience Profile. (160701)
- The Experience Profile currently only supports website visit interactions. If an interaction does not fully populate the facets required for a web visit, an error appears.
- [Fixed in XP 9.0 Update-1] The To date field must be filled in to see search results. This field is hidden by default and you must select the Filter button to enable it. (187153)
- It is not currently possible to search for contacts that do not have any interactions. (209041)
- The submit action on a form does not trigger the assigned event in FXM if the page is reloaded as a result of the submit action. (152376)
- Validation is not supported in this version of Marketing Automation, so users must ensure any dependent items are present and correct.
- Marketing Automation does not currently support Safari, so users must open the application in a different browser.
- [Fixed in XP 9.0 Update-1] If a campaign is inactive, the Move to another campaign activity pushes contacts all the way through the receiving campaign instead of holding the contact in the first activity of the inactive campaign until you activate it. (186685)
- Inactive campaigns cannot be deleted, so you must activate a campaign before you can delete it. (136658)
- [Fixed in XP 9.0 Update-1] You cannot listen for a combination of goals, outcomes, or campaign activities by using the And/Or toggle. The listener listens for an Or query by default. (186644)
- [Fixed in XP 9.0 Update-1] It is possible to enter an incorrect date for Delay or Listener activities, so users must validate the dates before activating campaigns. (154257)
- A copied campaign requires two submission attempts before the campaign successfully activates. (169235)
- [Fixed in XP 9.0 Update-1] The View contacts dialog box does not work in Cloud environments. (185958)
- [Fixed in XP 9.0 Update-1] You cannot create a campaign that contains multilanguage characters, for example, an umlaut or hieroglyph. If you try to save the campaign, the Campaign name is invalid error appears. (185923)
- [Fixed in XP 9.0 Update-1] The Change engagement score activity cannot subtract engagement points. It can only add engagement value points. (169936)
- The Path Analyzer does not correctly calculate the values for Experience Maps. (187166)
- When you submit a form, the Experience Profile displays incorrect URLs for the events. (166513)
- On the Form Performance tab, the metrics chart should be grouped by ID instead of field name. (167444)
- On the Performance tab, in the Metrics chart, values are formatted to have two decimal places. (166278)
- POST requests are sent when the xDB.Tracking.Enabled configuration setting is set to false. (166140)
- The required field validation is not registered or tracked as a field error. (160015)
- If a user tries to submit a form after a session has expired, the field tracking POST returns a 500 error. (159965)
- If a form is submitted with the default selected list item, no field metrics are recorded for the field. (161122)
- Confirming a password does not send the fieldId to the controller. (160016)
- Each selected check box increments the Completed metric for the field. (160014)
- The selected goal/campaign/outcome/page name does not show in the list of selected save actions. (158690)
- [Fixed in XP 9.0 Update-1] The number markup for min, max, step uses a dot (.) instead of a comma (,) as the decimal separator. (162729)
- [Fixed in XP 9.0 Update-2] Internet Explorer crashes when a user tries to close the Currency drop-down list. (166595)
- The Toolbox icon is missing in the Item Tree view. (154915)
- [Fixed in XP 9.0 Update-2] When a form is initially created in a language other than the default language (and the default language is not created), the form is in the general list of the Forms application. The form is available, but only displays for users who have the relevant selected client language in the Forms application. (183845)
- In CMS-only mode, the user can add the Trigger goal and Trigger campaign activity submit actions, but these are not tracked. This is intended behavior because CMS-only mode does not support these actions. When the form is published and submitted, an error displays. (179831)
- [Fixed in XP 9.0 Update-1] When a user sets multiple check boxes as being selected by default, the settings do not always apply correctly on the form because the form logic uses a dynamic data source. (173987)
- A user is not sent to the Login screen when a session ends. (171812)
- POST requests are still sent when the Xdb.Enabled and Xdb.Tracking.Enabled settings in the Website\App_Config\Sitecore\Marketing.xDB\Sitecore.Xdb.config file are set to false. POST requests should not be sent because there is no saved data. (166140)
- In Google Chrome, when a user starts filling in a date, a register request is sent for each entered digit of the year. This registers an incorrect completed field value in the form metrics. (173652)
- When the value of a radio button list is changed on a form, the value does not always register correctly in the form performance metrics. (165940)
- [Fixed in XP 9.0 Update-1] When a user navigates through a multipage form, every forward, back, or submit action is registered as a submit confirmation. This registers incorrect form metrics for the submit button(s). (160013)
- When using A to Z sorting on the forms list search field, the result shows forms that do not have an item and/or a display name. The sorting applies on the display name, which results in incorrect alphabetical ordering. (124756)
- In Google Chrome, the date component displays incorrectly in the forms builder. When you move the mouse over the up, down, and drop-down arrows, they do not function correctly. (173657)
- In Safari, the Apply and Cancel buttons in the context pane are not fixed at the bottom. (169465)
- When you set the data source for a form in the Content Editor, both the regular forms and the form templates are shown. Only regular forms should be shown. Note: A template is a regular form that is marked as a template. (176427)