A planning dataset is the key object for your planning.
Go to the Datasets tab within the 24Planning app and click “New” on the top right.
The following settings apply when creating a new dataset:
General Settings
-
Name: Name of the data set.
-
Zoom Level: This is deprecated and no longer used in the app.
-
Weight: The weight determines the order in which datasets are shown in the dataset dropdown selector in the planning view.
-
Time Highlight Preset: Optional custom 24Planning object. Highlights are shown in the planning board, e.g. you can define a highlight to show public holidays in the planning board. See below for more details on Time Highlight Presets.
-
Available View Presets: Defines the time windows that will be visible to the planner in the planning board, e.g. day, week, 2-weeks, month, etc.
-
Default View Preset: Default time window that is used when the planning board is opened.
-
Unplanned Work Sidebar Open: Check this box in case you want the unplanned work sidebar to be opened by default in case Unplanned Events is enabled on a datasource.
-
Mark Current Time: Check this box in case you want a marker on the current day in the planning view.
-
Load Chunk Size: If there are a lot of resources to load, they are loaded sequentially in chunks. Leave the value to default unless you experience loading issues.
-
Public Groups: Salesforce Public Groups are configured in the Users > Public Groups section in Setup. In the context of DataSets, only users belonging to the configured public groups will have access to the DataSet. If left empty, all users will have access to the DataSet.
-
Left Pane Default Width: Default width for the left sidebar when loading the page (in pixels).
View Presets are defined in Custom Metadata Types and go much further than defining the time window as described above. In fact, View Presets provide you great flexibility to customize the look-and-feel of 24Planning. Read more on View Presets in the next section.
-
Hide Time: Hide the event start date and time on scheduler event bars. Leave unchecked to show the time (default).
-
Bar Margin: Space in pixels between stacked event bars in the scheduler. Recommended range: 0–20 px. Defaults to 2 if left empty.
-
Row Height: Height in pixels for scheduler resource rows when this dataset is loaded. Recommended range: 20–120 px. Defaults to 50 if left empty.
Time settings
-
Start Day: The first day of the week that is shown on the planning board.
-
End Day: The last day of the week that is shown on the planning board.
-
Start Hour: The first hour of the day that is shown on the planning board.
-
End Hour: The last hour of the day that is shown on the planning board.
If you want to see full 24-hours range, you need to set both the Start Hour and the End Hour to '0' (zero).
These Time Settings are not the working hours of the resources, those are defined separately in workschedules as described further on. The Time Settings only impact the view in the planning board.
In other words, if an event lasts longer than the End Hour, it will not be automatically extended to the next working day by defining an End Hour. In order to get this behaviour you need to configure the Datasource in Duration Mode AND define an appropriate workschedule.
Resource Settings
-
Sort Resources by (DEPRECATED as of v5.7): Determines the order in which resources are displayed in the planner.
-
Data source and Alphabet: First group by data source and within a data source group alphabetically.
-
Alphabet: Rank alphabetically across all resources.
-
None: Rank alphabetically across all resources.
-
As of v5.7, the sorting mechanism has been updated in favor of a more flexible sorting and grouping mechanism defined via Dynamic Fields. Please consult the Dynamic Field section under Datasource for more information.
-
Only Show Occupied Resources: Only display those resources that are (partly) occupied during the corresponding time window, i.e. those resources that have Events assigned to them during the particular time window.
Related Objects
A dataset comes with a set of related objects, called datasources, that define the resources and their constraints, as described next.