Scheduling and Running Data Loaders
Notes:
Data Loading is currently in feature preview and as such documentation for this feature is still work in progress
Once a Data Loader is configured with sources, source items, and targets, it can be executed to import data into xpna. Data Loaders can be run on-demand or scheduled to run automatically.
Note:
Certain Data Loader types cannot be scheduled and require manual execution. For example, Upload-based Data Loaders require manual file uploads and must be run manually each time.
Running Data Loaders On-Demand
Data Loaders can be executed manually at any time from the Connections page.
From Excel Add-in
To run a Data Loader from the Excel Add-in:
- Navigate to the Connections page in the task pane
- Locate the Data Loader in the connected data sources list
- Click the Run button (play icon) to execute the Data Loader
For Data Loaders that require manual intervention (such as Upload types), the Data Loader dialog will open automatically, prompting for the necessary actions before execution can proceed.
From xpna Web
To run a Data Loader from xpna Web:
- Navigate to the Data Loader section
- Select the Data Loader from the list
- Click the Run or Execute button
Execution Process
When a Data Loader runs:
- Each configured source is connected
- Data is retrieved from each source item
- Data is validated against target mappings
- Valid data is imported into the xpna workspace
- Results and any errors are logged
Execution Time:
The time required to run a Data Loader depends on:
- The number and size of source items
- The amount of data being retrieved
- Network latency to source systems
- The complexity of target mappings
Monitoring Execution
While a Data Loader is running, progress can be monitored from the Connections page.
Activity Log
The activity log provides details about Data Loader executions:
- Start Time: When the execution began
- Duration: How long the execution took (or is taking)
- Status: Running, Completed, or Failed
- Records Processed: The number of records loaded
- Executed By: Which user initiated the run
Expanding Activity Details
Click on an activity log entry to see detailed information:
- Each source item's execution status
- The number of records retrieved and loaded per source item
- Any errors or warnings encountered during execution
- Duration for each step of the process
Scheduling Automatic Runs
Data Loaders can be configured to run automatically on a daily schedule.
Setting a Schedule
To configure a schedule:
- Navigate to the Connections page
- Locate the Data Loader in the connected data sources list
- Click on the schedule indicator or settings
- Configure the desired schedule time
Schedule Options:
- Daily: The Data Loader runs once per day at the specified time
- Time: The time of day to run (in the workspace's timezone)
Note:
Scheduled Data Loaders run in the background and do not require the Excel Add-in or xpna Web to be open.
Schedule Notifications
When a scheduled Data Loader completes:
- Workspace administrators receive an email notification
- The notification includes execution status and any errors
- The activity log is updated with the execution details
Data Loader Execution Results
After a Data Loader completes, the results can be reviewed.
Successful Execution
A successful execution indicates:
- All source items were retrieved successfully
- All data was validated against target mappings
- All valid records were imported into xpna
- No critical errors occurred
Partial Success
A partial success indicates:
- Some source items were retrieved successfully
- Some records were imported, but others were skipped
- Non-critical errors or warnings occurred
Common Warnings:
- Dimension values not found in xpna (if configured to skip)
- Records with missing required columns
- Data type mismatches that were handled
Note:
Workspace administrators will receive an email notification on repetitive failures to alert them of ongoing issues that require attention.
Failed Execution
A failed execution indicates:
- One or more source connections failed
- Critical errors prevented data from being imported
- Configuration issues that must be resolved
Common Failure Reasons:
- Source connection errors (invalid credentials, network issues)
- Missing required target column mappings
- Invalid data that cannot be processed
Troubleshooting Execution Issues
If a Data Loader fails or produces unexpected results:
Check Source Connections
Verify that:
- Source credentials are still valid
- Source systems are accessible from xpna
- Required permissions are still in place
Review Target Mappings
Ensure that:
- All required columns are mapped
- Dimension mappings are correct
- Column data types match expectations
Examine Activity Logs
Review the activity log for:
- Specific error messages
- Which source items failed
- The number of records processed vs. expected
Test with Sample Data
Before running a full load:
- Use the Test button in Source Items to load sample data
- Verify that sample data looks correct
- Check that all columns are present and formatted properly
Best Practices
To ensure reliable Data Loader execution:
Configuration
- Test all source connections before saving the configuration
- Verify target mappings with sample data
- Use descriptive names for Data Loaders to identify their purpose
- Document any custom SQL queries or complex mappings
Scheduling
- Schedule Data Loaders to run during off-peak hours
- Stagger multiple Data Loader schedules to avoid overlapping executions
- Allow sufficient time between connection refreshes and Data Loader runs
Monitoring
- Regularly review activity logs for errors or warnings
- Set up email notifications for failed executions
- Monitor the number of records being loaded to detect unexpected changes
Maintenance
- Update source credentials before they expire
- Test Data Loaders after source system changes
- Review and update target mappings when dimension structures change
Getting Help
If issues persist or assistance is needed with Data Loader configuration:
Contact xpna support via email to support@xpna.com with:
- The Data Loader name and workspace
- A description of the issue or expected behavior
- Any error messages from the activity log
- Screenshots of the configuration (if applicable)
Note:
xpna support can assist with advanced configuration scenarios, custom stored procedures, and troubleshooting complex data loading issues.