- 1E 23.7 (SaaS)
- 1E Experience Analytics
- Troubleshooting
- Known issues
Known issues
Lists of the current known issues with implementing, configuring, and using Tachyon Experience.
If you cannot find an issue and its workaround on this page, please
refer to 1E platform - Known issues for the Platform and other applications
try searching the 1E Support Portal (https://1eportal.force.com/s/tachyontopicdetail) for issues that have hotfixes.
If you need further help, please refer to the Troubleshooting page for how to contact 1E Support and the technical support process.
Issue | Description | Workaround |
|---|---|---|
Experience - Software > Duplicate row for a product is displayed on Software screen when architecture column is added from column picker following an upgrade from 8.0. | The architecture column did not exist in pre-v8.0 SoftwarePerformance table. When upgraded to v8.0 or later, architecture column has been introduced as nullable column to accommodate pre-upgrade data. It will be set as null for all existing data from before the upgrade. Gradually as new experience performance data comes in post upgrade architecture will now be included. This means that for 90 days after the upgrade aggregations within the Software screen of experience can have two entries, one with an unknown architecture and one with a valid architecture. | The existing data will correct itself 90 days after the upgrade. If you need to fix this issue in the meantime, a maintenance Stored Procedure for the Experience database can be obtained from 1E. The SP will update the null architecture for pre-upgrade software performance rows by using post-upgrade rows to identify and correct old software architectures. |
Experience Analytics - Tiles have an additional text "score" added to them when view between saved preset is changed. | When user changes the view between Default and user saved presets; an additional text "Score" gets added to the tile title, e.g: StabilityScore, ResponsivenessScore. | Refreshing the browser removes the additional text "Score". |
A survey that has been dismissed by the user will reappear if it is disabled then re-enabled. | If a user engagement (survey or announcement) is disabled then re-enabled then it appears to the 1E Client as a completely new engagement and the previous state (dismissed, in this case) is lost. | Do not disable an engagement then re-enable it! In effect this creates a new instance, at least in terms of data sent to the 1E Client. |
Application Interaction table can contain processes reported as *.tmp files where the Product and Version columns are blank. | The Application Interaction view is reached by launching the Experience > Devices and viewing the Device hyperlink. When viewing the Experience > Application Interaction tab, the *.tmp records are also displayed which do not have associated Product or Version details. These should be filtered out. | None |
The Survey response page displays responses from a device that do not match the score seen when viewing the Device details due to duplicate survey names | When a survey is deleted, the old responses do not get removed and current behavior causes issues when a new survey is created with the same name. The calculations for sentiment score includes responses from the old survey where the names match. | Where this occurs, recreate the survey using a unique name that has not been previously used. If you are affected by this, please contact 1E Support for additional help. |
When doing a search on Survey page, the page size resets back to the default (50) | On the Experience > Survey page, the page size can be increased to to display 100 or 250 rows. However, when a search is performed on the page, the page size jumps back to the default 50. | None |
Survey reports always shows Applicable devices as 100% | Even when a general purpose survey has been assigned to a Management Group, the filter for survey reports always shows 100% for Applicable devices and not consistent with the devices assigned to the selected Management Group | None |