cancel
Showing results for 
Search instead for 
Did you mean: 

URGENT! Help Required - Not able to see LOCALE fields in Story Reports in LMS Schemas

vtamil
Participant
0 Kudos
267

Hello Experts,

We are creating story reports for LMS. I need to include the following fields in the report: I was not able to find the following 3 fields in the story reports:

1. Item Title - Translations (Item > Item Title (Translation))

2. Active Locale ID - Located in ( User > Preference > Active Locale ID)

 

vtamil_0-1722993455503.png

 

View Entire Topic
SF-Dan
Product and Topic Expert
Product and Topic Expert

Not all LMS DB fields will be available in SAC, see Available Data (Schema) in Story Reports | SAP Help Portal 
Some fields like locale translations are dynamically selected based on the current user's preference in Platform.
You can create custom BIRT reports using Plateau Report Designer against more LMS DB fields.

vtamil
Participant
0 Kudos
Thank you for your prompt response. Well, we already have a BIRT report and attempting to create a story reports version replicating the PRD. I understand, about the current user preference's but i have a requirement to track the Item ID's information, including the translations done. Do we have any other options ?
SF-Dan
Product and Topic Expert
Product and Topic Expert
You should be able to create the BIRT reports against the item i18N (localization table) and the student user preference tables. Post in https://community.sap.com/t5/sap-successfactors-learning-custom-report-exchange/gh-p/hcm-learning-cu... if you need guidance on that, but for SAC you will just have to wait if they provide any enhancements in the roadmaps for additional data fields to be made available.
vtamil
Participant
0 Kudos
Would you be able to understand the process of syncing LMS tables into SAC ? Is all of the fields provided in the LMS system are available in SAC, do we have any backend mechanism control
SF-Dan
Product and Topic Expert
Product and Topic Expert
0 Kudos
No Not all LMS DB fields are available/exposed in SAC because it requires development to enhance certain aspects and develop the API calls accordingly in the backend. These would require enhancement requests whihc may mean some will never get included if there is not a big need for the particular data in the way SAC is designed to be used similarly like LMS standard audit reports vs UI or LMS BIRT custom reporting, or other Data Services, etc...