Can we have a formula that will enable us to calculate the working hours/mins (based on a 7hrs working day) between them. We must take into account that the two dates/times may span more that one day.
Noted. Would a simple 5-day week with optional hours-per-day function work, or is a system accurately representing the national holidays for a given country required? The latter would be far more complex and would need significant demand to be developed.
If both dates are date+time values, you'd need to specify not just the length of the working day, but also the start time and end time, in case some values were at times outside working hours.
An extension of this is the ability to determine whether dates are workdays in a table, port those to a graph and omit none working days from the time axis. this would eliminate flat spots, or flat intervals, in a time graph. Unless of course this is already possible.
This is oversimplistic in that it will not account for bank holidays, but it will enable you to filter so that you only have dates which fell on Mon-Fri... hope that helps?
Thanks for the post Guy. I have a formula which determises the day of the week and from there I can filter as needed. My real problem, forgive me this wasn't clear in my post, is that of flat intervals. Tables containing financial data are null for the weekends. Omniscope retains the date in the axis in graph view but has nothing to plot. This results in a horizontal line drawn from the last data point on the Friday to the first data point on the Monday. What I would actually like to do is remove any null dates from the axis which should then remove all the flat intervals, essentially joiing the Friday point to the Monday point. This would provided a clearer view of the data being presented and remove all unnecessary dates.
You could use formulas to ensure even intervals on the X axis, but you would lose the date values. Really, this is a feature request for a working days date scale in the graph axes.
As a workaround you could have a separate field which is a textual representation of the date and set this to be categories. If you set the x-axis to be this field you would not see any dates which did not have values, which would fix the problem as long as all the other dates had values.
You would need to set the date format of this textual representation to be something which is correctly sortable as text, such as "yyyy-MM-dd" (sorts by year first, then month, then date, because text is sorted using the characters from left to right), to ensure you did not have to go in and manually order the dates.