I came across this also. That's because of the order in which the view fiel where declared in hr_schedule/__opernerp__.py. it appears that an id was requested before it was even declared. rearranging worked for me. this workede for me
'data': [ 'wizard/schedule_ot_by_employees.xml', 'hr_schedule_view.xml', 'security/groups.xml', 'security/ir.model.access.csv', 'security/ir_rule.xml', 'data/hr_schedule_data.xml', 'wizard/validate_schedule_view.xml', 'wizard/compute_alerts_view.xml', 'wizard/generate_schedules_view.xml', 'wizard/restday_view.xml', 'hr_schedule_data.xml', 'hr_schedule_workflow.xml', 'hr_schedule_cron.xml', 'schedule_ot_batch_workflow.xml', 'schedule_ot_workflow.xml', 'alert_rule_data.xml', ],
I came across this also. That's because of the order in which the view fiel where declared in hr_schedule/ __opernerp_ _.py. it appears that an id was requested before it was even declared. rearranging worked for me.
this workede for me
'data': [
'wizard/ schedule_ ot_by_employees .xml',
'hr_schedule_ view.xml' ,
'security/ groups. xml',
'security/ ir.model. access. csv',
'security/ ir_rule. xml',
'data/ hr_schedule_ data.xml' ,
'wizard/ validate_ schedule_ view.xml' ,
'wizard/ compute_ alerts_ view.xml' ,
'wizard/ generate_ schedules_ view.xml' ,
'wizard/ restday_ view.xml' ,
'hr_schedule_ data.xml' ,
'hr_schedule_ workflow. xml',
'hr_schedule_ cron.xml' ,
'schedule_ ot_batch_ workflow. xml',
'schedule_ ot_workflow. xml',
'alert_ rule_data. xml',
],