hierarchy of group descriptions

[Gareth McNicol]

Is it possible to have the schedule view show a hierarcy of group descriptions where each group has it's own sub groups?

For example can we have it for several Dentist Surgeries that have different dentists that can have appointments assigned from a central location

The hierarchy would be

DateGroupDescription
- Surgery A
-- Dentist A
-- Dentist B
-- Dentist C
- Surgery B
-- Dentist D
-- Dentist E

This would allow us then to filter on Surgeries, amongst other requirements that we need to fulfil.

[Rosi]

Hi Gareth,

This feature is not supported by RadScheduleView . You can vote for it here.

Kind regards,
Rosi
the Telerik team

[Gareth McNicol]

No I can't; the vote link comes up with an error

[Hristo]

Hello Gareth,

Actually this feature is supported out-of-the box.
What you need to do is to add Resources to Appointments - in your case some appointments will have Resource SurgeryA and some Denstist Resource, while other will have Resource SurgeyB and some Dentist Resource. Then you could specify in GroupDescriptors property of RadScheduleView the hierarchy - you will first add DateGrupDescriptor, then ResourceGroupDescriptor with ResourceType="Surgery" and last again ResourceGroupDescriptor with ResourceType="Dentist".
The only limitation is that there is no way to specify that in SurgeryA you will have only Dentist A,B,C and in SurgeryB you will have only Dentist E,F. You will have all dentist resources in all surgery resources.

Here is a xaml snippet how to achieve your task:

<Window x:Class="WpfApplication1.MainWindow"
        xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation"
        xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml"
        Title="MainWindow" Height="600" Width="800"
        xmlns:telerik="http://schemas.telerik.com/2008/xaml/presentation">
    <Grid>
        <telerik:RadScheduleView>
            <telerik:RadScheduleView.ViewDefinitions>
                <telerik:DayViewDefinition />
                <telerik:WeekViewDefinition />
                <telerik:MonthViewDefinition />
                <telerik:TimelineViewDefinition />
            </telerik:RadScheduleView.ViewDefinitions>
            <telerik:RadScheduleView.GroupDescriptionsSource>
                <telerik:GroupDescriptionCollection>
                    <telerik:DateGroupDescription />
                    <telerik:ResourceGroupDescription ResourceType="Surgery" />
                    <telerik:ResourceGroupDescription ResourceType="Dentist" />
                </telerik:GroupDescriptionCollection>
            </telerik:RadScheduleView.GroupDescriptionsSource>
            <telerik:RadScheduleView.ResourceTypesSource>
                <telerik:ResourceTypeCollection>
                    <telerik:ResourceType Name="Surgery">
                        <telerik:ResourceType.Resources>
                            <telerik:Resource ResourceName="Surgery A" />
                            <telerik:Resource ResourceName="Surgery B" />
                        </telerik:ResourceType.Resources>
                    </telerik:ResourceType>
                    <telerik:ResourceType Name="Dentist">
                        <telerik:ResourceType.Resources>
                            <telerik:Resource ResourceName="Dentist A" />
                            <telerik:Resource ResourceName="Dentist B" />
                            <telerik:Resource ResourceName="Dentist C" />
                            <telerik:Resource ResourceName="Dentist D" />
                            <telerik:Resource ResourceName="Dentist E" />
                        </telerik:ResourceType.Resources>
                    </telerik:ResourceType>
                </telerik:ResourceTypeCollection>
            </telerik:RadScheduleView.ResourceTypesSource>
            <telerik:RadScheduleView.AppointmentsSource>
                <telerik:ObservableAppointmentCollection>
                    <telerik:Appointment Start="2011/02/24 00:00:00" End="2011/02/24 02:00:00" Subject="App1">
                        <telerik:Appointment.Resources>
                            <telerik:Resource ResourceName="Surgery A" ResourceType="Surgery" />
                            <telerik:Resource ResourceName="Dentist A" ResourceType="Dentist" />
                        </telerik:Appointment.Resources>
                    </telerik:Appointment>
                    <telerik:Appointment Start="2011/02/24 02:00:00" End="2011/02/24 04:00:00" Subject="App1">
                        <telerik:Appointment.Resources>
                            <telerik:Resource ResourceName="Surgery B" ResourceType="Surgery" />
                            <telerik:Resource ResourceName="Dentist A" ResourceType="Dentist" />
                        </telerik:Appointment.Resources>
                    </telerik:Appointment>
                </telerik:ObservableAppointmentCollection>
            </telerik:RadScheduleView.AppointmentsSource>
        </telerik:RadScheduleView>
    </Grid>
</Window>

I hope that this is acceptable for you.
p.s. the link with the PITS item is active.

Best wishes,
Hristo
the Telerik team

[Gareth McNicol]

Consider:

Surgery A is in London England.  Dentist A and Dentist B work there. They cannot fly for medical reasons.  (I know, sad).  They can only operate out of Surgery A.

Surgery B is in Brisbane Australia (GO LIONS!), about as far away as you can get on an aeroplane.

Your solution would show *a particular* Dentist A-E in Surgery A and a different Dentist A-E for Surgery B.

The list of Unassigned appointments is in a list box, waiting to be dragged on to the Schedule View.  The operator of the software knows what city the appointment is for but the available dentists in both surgeries should only be available in their respective places of work.

In case you hadn't guessed - my solution actually refers to FIXED assets in a hierarchy of locations.  Filtering on the hierarchy would also be ideal.

[Hristo]

Hello Gareth,

Thank you for your feedback.

I understand your case but until we support hierarchy this will not be possible directly.
However you can still produce behavior similar to what you want using few tricks. For example you could use GroupHeaderStyleSelector and Collapse the D, E groups when their parent is Surgery A and then collapse A,B,C when parent is Surgery B. I know that this is not as efficient as build-in hierarchy but at least it is a solution.

As for the drag-drop operations - you could override it and allow only drop of appointment based on appointment and group properties.

Filtering Groups is possible using GroupFilter property but it will not help in your case. With its current implementation you don't have enough information on which to decide if this group will be filtered or not.
We should definitely look for improvements in this area. 

Kind regards,
Hristo
the Telerik team

[Vadim]

Hristo,

I have similar hierarchy problem and trying so i am trying to implement your work-around. 

My question is: how can i "collapse" group using GroupHeader style?

So far i was only able to make header of that group disappear, but not corresponding row/column.

[Yana]

Hi Vadim,

For now the needed approach cannot be achieved with RadScheduleView even with GroupHeaderStyleSelector - we're sorry for our confusion.  Implementing hierarchy of group descriptions is in our plans and we'll do our best to provide the feature for some of the upcoming releases.

Greetings,
Yana
the Telerik team

[John]

Just want to know whether this feature has been implemented in the latest version of RadScheduleView 

[Rosi]

Hi,

This issue is still not part of the built-in functionality of RadScheduleView.

I suggest you review our SDK examples:

Grouping and filtering with tree view - This example demonstrates grouping and filtering with TreeView control.

Hierarchical Grouping And Filtering With TreeView - This example demonstrates hierarchical grouping and filtering using TreeView control.

Also, you can consider using RadGanttView control which supports hierarchy.

Hope this helps.

Regards,
Rosi
Telerik