Future Proof Your Holiday Forms

wilkies0106aw — Fri, 04 Jul 2014 08:48:25 GMT

All,

I want to pick your brains if I may.

SP 2010
InfoPath 2010 (web based browser form)

I’m rebuilding our Holiday Request form – simple enough.

I’m not having a Date From or a Date To field on my form instead I’m using a repeating table so that each date is entered/applied for individually.

This mirrors our timesheet application (3rd party – not InfoPath/SP based.)

The hope is we can somehow interrogate the InfoPath form and marry it up line by line with what was or not entered into our timesheet system. This will most likely be done via SQL if that’s possible i.e. SQL can read a repeating table.

Anyway,

I’m thinking about how best to represent holiday entitlement figures and cut down on yearly maintenance.

On my form I have to run at least 2 years consecutively i.e. 2014 and 2015. The year is selected via a drop down control (connected to a SP list).

Not all my offices use the same year i.e.

Office 1 – year is Jan 1 – Dec 31 of this year i.e. calendar year –
Office 2 – they straddle 2 years i.e. April 1st 2014 – March 31 2015 –

Plus you generally book holiday in advance.

Hence the drop down.

I have another list called User Entitlement.

Ideally I don’t want to continually update this list each year with new year based columns

i.e.
2014 Holiday Entitlement
2015 Holiday Entitlement
2016 Holiday Entitlement

2014 Holiday Taken
2015 Holiday Taken
2016 Holiday Taken

2014 Holiday Remaining
2015 Holiday Remaining
2016 Holiday Remaining

If I have it as above I’ll have to keep updating my form year on year to look at new columns etc, show the maths etc, update workflows

How might I achieve what I’m after?

Does anybody have just 2 columns i.e. - this year, next year and run with it? I guess you’d have to run a workflow at X point in the year to move the values from next year to this year.

Alternatively how do you future proof your holiday request system?

General

Future Proof Your Holiday Forms