Extracting custom field data from SCORM files

Hi ​@joymiegarcia ,

You've hit a very common wall when it comes to SCORM reporting in Docebo. The short answer is that there is no native "bulk export" for cmi.interactions (which contains your text entries, timestamps, and question attempts) in Docebo's standard Custom Report Builder.

Why this happens: SCORM 1.2 and 2004 treat interaction data as a serialized data string designed for the course to remember where a user left off, not to act as a queryable database. Because of this, Docebo’s UI only exposes this granular data in the individual user drill-down view.

Solution 1: The API Route (For existing SCORM courses) To get this data out in bulk, you will need to rely on the Docebo API. It requires building a looping architecture (using a custom script or a tool like Docebo Connect) that:

1. Retrieves a list of users enrolled in the course.

2. Identifies the specific SCORM learning object ID.

3. Loops through each user to retrieve their specific SCORM interactions list, pulling those individual JSON responses and flattening them into a single CSV. It’s a bit of heavy lifting, but it’s the only way to extract historical SCORM interactions in bulk.

Solution 2: Transition to xAPI (The long-term approach) Before investing heavily in API automation, have you considered publishing future modules as xAPI (Tin Can) instead of SCORM?

In organizations I've worked with that require deep, question-level analytics for compliance or performance reviews, the pattern that holds up best is transitioning to xAPI. Every action (e.g., "User entered text X into Question Y") is recorded as a discrete data statement in Docebo's built-in Learning Record Store (LRS), rather than being trapped in a serialized string.

The Drawbacks to xAPI you should know: While xAPI captures the data beautifully, it isn't a magic bullet:

1. No historical fix: It won't help you retrieve data for your existing SCORM courses.

2. Reporting UI limitations: Docebo captures the LRS statements, but the native Custom Report Builder still doesn't natively map all raw xAPI verb statements into a simple visual table. To run complex analytics on specific text-entries and question statements, you generally need to use Docebo's LRS forwarding to send that data to an external Learning Record Store or BI tool.

You can read more about how Docebo handles xAPI uploads and its internal LRS requirements here: Uploading xAPI (formerly Tin Can API) content – Docebo Help Center.

Hope this helps clarify the platform's constraints and points you in the right direction!