We’re experiencing issues with our labor analytics dashboard exports in HM 2022.2. When we export reports to Excel, shift differential and overtime hours are missing from the output file, even though they display correctly in the dashboard view.
The problem seems related to our custom date filter logic - we have filters set for weekly payroll periods (Sunday-Saturday), but the export only captures regular hours. We’ve checked the report template mapping and confirmed all fields are selected, but the export field configuration doesn’t seem to respect the template settings.
This is causing major payroll compliance issues since we need accurate overtime data for weekly reporting. Has anyone encountered similar export problems with labor analytics?
I’ve seen this before. Check your export template configuration - there’s often a mismatch between dashboard field mappings and export field definitions. The shift differential fields might be using calculated columns that aren’t included in the default export schema.
The root cause here is the disconnect between dashboard rendering and export processing. Let me walk through the complete solution addressing all three areas you mentioned.
Custom Date Filter Logic Fix:
First, verify your date filter definitions align between dashboard and export. Navigate to Labor Analytics > Filter Configuration and ensure your weekly payroll filter explicitly sets:
- Start: Current week Sunday 00:00:00 EST
- End: Current week Saturday 23:59:59 EST
- Timezone: America/New_York (hardcoded, not system default)
The export module needs these exact parameters or it reverts to default calendar week logic.
Report Template Mapping:
Your template needs to include calculated field definitions. Edit your labor report template (Administration > Report Templates > Labor_Analytics_Weekly) and add explicit mappings for:
- Shift differential hours (calculated as: hours worked between 18:00-06:00)
- Overtime hours (calculated as: total hours - 40 for weekly period)
- Overtime pay (calculated field: OT hours * base rate * 1.5)
These can’t just be selected checkboxes - they need formula definitions in the template XML that the export engine can process.
Export Field Configuration:
This is the critical piece. The export configuration file (typically AnalyticsExportConfig.xml in your HM config directory) needs explicit field mappings that reference your template calculations. You’ll need to add entries like:
<field name="shift_differential" source="calculated" formula="SHIFT_HOURS_CALC"/>
<field name="overtime_hours" source="calculated" formula="OT_HOURS_CALC"/>
<field name="overtime_pay" source="calculated" formula="OT_PAY_CALC"/>
Without these export field definitions, the export engine ignores calculated columns even if they’re in your template.
Validation Steps:
- Update your weekly filter to use explicit EST timezone (fixes boundary issues)
- Add calculated field formulas to your report template (ensures calculations are defined)
- Map those fields in AnalyticsExportConfig.xml (tells export engine to include them)
- Test with a single week’s data first to verify all hours export correctly
- Check that timezone conversion is consistent - export timestamps should match dashboard display
The payroll compliance issue should resolve once export processing uses the same calculation logic as dashboard rendering. The key is making those implicit dashboard calculations explicit in the export configuration.
After implementing these changes, restart your analytics service to reload the configuration. Your Excel exports should then include all shift differential and overtime data matching what you see in the dashboard view.
Good catch on the timezone - I checked and we are using EST for dashboard but export might be UTC. How did you fix the template mapping issue? Our overtime fields are calculated (regular hours * 1.5 rate) so that could explain why they’re not exporting.
For calculated fields in labor analytics, you need to explicitly map them in the export configuration XML. The dashboard can display calculated values, but export requires those calculations to be defined in the template. Check your AnalyticsExportConfig.xml file - you’ll probably need to add formula definitions for shift differential and OT calculations there, not just select the fields.
I’d also verify your date range parameters. Custom weekly filters (Sun-Sat) sometimes don’t align with the default export date logic which uses calendar weeks (Mon-Sun). This causes boundary issues where Friday overtime might get excluded if it falls on a filter edge. Your report template needs explicit start/end date parameters that match your payroll period definitions.
We had a similar issue last quarter. The problem was that our custom date filters were using different time zones for display vs export. Dashboard showed correct data in local time, but export defaulted to UTC, which shifted some overtime hours into different pay periods. Verify your filter logic handles timezone conversion consistently across both views.