SAP Knowledge Base Article - Public

3050294 - Stories in People Analytics - Known Issues

Symptom

This Knowledge Base Article (KBA) lists the most reported issues for Stories in People Analytics.

In the spirit of transparency and mutual success, we sincerely appreciate your partnership as we, together, identify and report the status of issues associated with these releases.

If you are looking for a list of defects which have been identified as part of the latest release, please check the KBA: 2692971

Environment

  • SAP SuccessFactors People Analytics
  • SAP SuccessFactors HCM Suite

Resolution

 Open Issues

NumberIssueSteps to Reproduce the issueWorkaround in KBAInternal Tracking IDStatus 
1Reports are automatically shared with end-users 
  • Import a report from Content Store.
  • You will see a shared icon beside the report but you have not shared the report with any user.
3042987FPA81-6336Open
2Customised & Renamed Template from Content Store Overwritten When New Import of Template from Content Store is Completed
  • Import report from Content Store
  • Rename template from Content Store 
  • Edit the renamed report & customise the report. 
  • Save the Report 
  • Import same original report from Content Store
  • Original report is overwritten with original report template from Content Store
3022943

AYT-35326

FPA82-3592

Open
3When you create queries using columns from various connected tables (auto joins), your browser might crash with an Out of Memory error message.. Hence, the "SourceQuery" must be OptimizedWhen you edit a Story, the "sourceQuery" attribute, value of which has about 150,000 characters,  this attribute seems to be added twice for each of the queries in the batch. This need to avoided to make the request size half. 3071139FPA87-3840Open
4Getting SAC page intermittently instead of People Analytics query designer page

While trying to create a new story from Report Center, user is navigated to SAC page intermittently. 

[Update]Clicking browser Back button after opening a Story frequently leads to this screen and not report centre.

Complete a hard refresh of the browser Ctrl + Shift + R. Do not use the back button function and only navigate using SuccessFactors UI. 

3032117

AYT-32196

FPA87-1588

Open

5

Cannot find Autojoin columns in Advanced Filtering in Stories.

Some fields are missing in Advanced Filtering e.g. Business Unit, Department, Location

  1. Create a new Story report
  2. In the query designer select a table e.g. Job Information
  3. Select a couple of fields e.g. Business Unit Code and Name
  4. Go to Advanced Filtering
  5. Try to apply a filter on these fields
  6. Cannot find the fields Business Unit Code or Name
3075040FPA00-22267Open
6
Query Designer Changes are not reflected in Story Designer
  • Go to reporting
  • Edit a Story Report
  • Edit the Data Source
  • Add a field
  • Click on Finish
  • See that newly added fields are available for aggregated tables but not for non-aggregated:

3117183

FPA10-4384Open
7
Divide operation in calculated column of Report story throwing error
  1. Login to SuccessFactors BizX and go to Report Center
  2. Create a simple story with below calculated column condition
  3. ([value1]/[value2])*100
  4. Preview the query

3091338

FPA58-1597 / FPA97-113Open
8

Child Object Fields are not getting displayed in the Query Validation Tool Edit Screen.

  1. Create Story with Education object e.g Employee Profile#Background Information#Education
  2. Now rename the new column
  3. Navigate to the Admin Center --> Manage Business configuration -->Employee Profile --> Background Elements --> education
    here rename to some other name
  4. Now Run or Edit the story from Report Center here you can see the error message
  5. Navigate to the Query Designer and then preview
  6. Now Query Validation Tool check the fields from "User Information" Composition(Child) object are not displaying only Child Object name is displaying

3121525

AYT-45713Open
9
Header labels are not being translated on People Analytics Story reports.
  1. Create a data source on one language e.g. English.
  2. Add fields to the query and add to a table widget and save the story
  3. Go to the settings from SuccessFactors and change the language e.g. Portuguese
  4. The column headers will not be translated, only the data within the output of the report
 3085179FPA00-43001Open
10
Duplicate records in Story report due to selection of Foundation object fields
  1. Create a story report by selecting fields like Assignment ID and Foundation object fields from Non-MDF object
  2. In the output we can see there are multiple records for a user.
3211995

FPA97-4236

AYT-45442

Open
11

When we create a simple Story report on fields like Business Unit Name, Department Name, Cost center Name so on, and Preview the Query in the output we can see ID's instead of Values.

  1. Create Simple Story report on Job Information object and
  2. Select fields like Business Unit Name, Department Name, Cost center Name
  3. Under Selected Columns Semantic Type is showing as Measure by default
3245500

FPA89-2748

FPA89-2597

AYT-50083

Open
12

SAC Query Designer Behavior when qualifying a Boolean column as a dimension or measure

  1. Create a new Story report
  2. Select Boolean field like vacant from Position object
  3. Click on Column overview Section 
  4. Can see field semantic Type is shown as Measure
3252793

FPA89-2597

AYT-50083

Open
13

Labels in Foundation Objects (such as Location, Pay Component etc.) in Stories are not getting changed when you change the system locale to another language.

 3338484ECT-209058 Tentative 2505
14

When Country Specific Compensation Information object is linked with Job Information --> Compensation Information object in Query Designer of Story report, duplicate records are visible in the output for some users.

  1. Create a new Story report
  2. Link Job Information with Compensation Information object in Query designer.
  3. Can see only one record in output
  4. If we add Country Specific Compensation object to link, then we can see multiple records in output.
3448915

ECT-234050 

Open
15

No data in "National ID Card Type" field in Story Report

1. Login to the instance
2. Navigate to Report Center
3. Create New/Edit the affected Story Report 
4. Add the "National ID Card Type" field from "National ID Information" Object 

5. Observe that in few particular scenarios the "National ID Card Type" field is blank.

  • SCENARIO 1: Default label of Card Type
  • SCENARIO 2: For any new label added through data model
  • SCENARIO 3: Any existing label change for any particular locale
  • SCENARIO 4: Any deletion of locale-label
3465748

ECT-232054, ECT-216765 

Tentative 2505
16.

When Employment Details fields are selected from the Job Information object in a Story report, they do not respect RBP



  1. If permissions for fields from (Employee data -> Employment details) are not provided, these fields appear greyed out in the canvas report.
  2. In a Story report, if the Employment Details fields are selected from the Job Information object, there is no lock symbol displayed for these fields.
  3. Data is available to all users even though there are no Role-Based Permissions (RBP) set, or they are restricted.
  4. However, if these fields are selected from the Home Assignment object, the correct behaviour is observed.
3570106

ECT-244576

 

2505

 

Resolved Issues

NumberIssueSteps to Reproduce the issueKBAInternal Tracking IDStatus 
1

Story report is not following RBP of Foundation Object's override restrictions.

1. In the RBP role, under Miscellaneous Permissions category - Position Object - one of the foundation objects (Ex: Pay Grade column) has been restricted.
2. The pay grade column permission has been mentioned as 'NO ACCESS' in the role as shown above or READ ONLY to specific target population.
3. That means, story report should not fetch the data of Pay Grade column of Position object/should not fetch for target population which restricted.

To verify that,

1. Go to report center.
2. Create a new Story report.
3. Select Position domain - select Pay Grade column.
4. Story report fetch the data for Pay Grade column in the report.

3338743AYT-52803Fixed in 2405
2

Custom schemas are missing under 'Create Story' Permission in RBP

  1. Navigate to Manage Permission Role
  2. Edit an existing role/create a new role
  3. Click on permission -> Go to Report Permission section. 
  4. Custom schemas are missing under 'Create Story' Permission.
3453242

INC7862106, AYT-55493

Fixed in 2411

See Also

3074269 - Report Stories will no longer be lost when user is deleted from SAP Analytics Cloud (embedded) system after IPS User Sync 

3074043 - How to Sync one user in IPS - People Analytics 

3025688 - People Analytics Story - Columns limits for Story Creation

3071139 - Out of Memory issue for People Analytics Report Stories for Complex Stories

2993273 - Data Model, Metadata or Configuration changes not applying for existing Story queries - People Analytics

3022943 - Customised & Renamed Template from Content Store Overwritten When New Import of Template from Content Store is Completed

3025334 - Imported Reports from Content Store show a shared icon

3091338 - Divide operation in calculated column of Report story

3117183 - Query Designer Changes are not reflected in Story Designer

3075040 - Columns missing Advanced Filtering - People Analytics

3032117 - User intermittently gets SAC page and the message "The resource does not exist, or you do not have permission to read it" - People Analytics Report Story

Keywords

People Analytics, Report Stories, SAC, PARS, Embedded Analytics, Stories, Known Issues, Fixes, Workaround , KBA , LOD-SF-ANA-SAC , Stories in People Analytics , Problem

Product

SAP SuccessFactors HCM Suite all versions