[FEATURE] [Scheduler] Feature

[Thomas-see]

Which PCF Component
Scheduler
Is your feature request related to a problem? Please describe.

Yes. The Scheduler PCF currently requires a parent resource lookup field in order to associate events with resources. I understand that the control was not originally designed around a simple 1:N Dataverse relationship model. However, in many real-world Dataverse scenarios (such as venue booking systems), resources already have a direct one-to-many relationship with events, so requiring a parent resource lookup adds configuration overhead that isn’t needed in these cases.

Describe the solution you'd like

1. Allow Resource Assignment Without a Parent Resource Field

I would like the control to support a simple scenario where:

A Resource (Venue) table

Has a 1-to-many relationship

With an Event (Booking) table

And the event record contains a lookup like:

event.<venueid> = resource.cr0f6_bookings_venueid

In this configuration, the Scheduler should be able to display venues as resource columns without requiring a parent resource field, and should automatically group events under their respective resources based on the lookup.

This would allow the control to work out-of-the-box with standard Dataverse relationships.

2. Ability to Open Resource Records from the Scheduler

When a user clicks a event (booking) (e.g., the name of a booking), it would be extremely helpful if the scheduler triggered navigation to the corresponding Model-Driven App form, for example:

Xrm.Navigation.openForm({
    entityName: "cr0f6_bookings",
    entityId: "<booking GUID>"
});

This would enable full integration with MDA forms and let users quickly open and edit the booking from the scheduler display.

Additional context
We are using the Scheduler PCF as a venue booking calendar.
Each venue (resource) can have many bookings (events).
The 1:N relationship structure is perfectly suited to this PCF, but the current parent-resource requirement makes the setup more complicated than necessary.

Here is a screenshot showing how the scheduler is being used in our scenario: