Displays a calendar or schedule.
The first type is a calendar with weekdays as columns.
You can use the calendar setting Show checkboxes to enable checkboxes on a menu item.
The calendar menu item can pass the ids of its selected calendar items, for historical reasons commonly referred to as selecteditems via links from the calendar to other menu items. These menu items then access these ids as a comma-separated string.
Checkboxes use the values from the first calendar item column as calendar item ids. Calendar item ids must be unique unless they are NULL. Any calendar item with NULL in the first column will not show a checkbox.
The calendar item ids that you access through selecteditems are ID values of calendar items that were valid when the user loaded the calendar. No validation is performed to ensure that the ID values are still valid, that their calendar items would still be visible if the user reloads the calendar.
For example, you have a calendar of meetings and a top-link "Postpone all checked meetings by one month". The user checks a few calendar items and then clicks the top link. Now, the checked meetings are postponed , and their calendar items will no longer appear in the calendar, but the calendar still remembers the IDs of the checked calendar items. If the user checks a few more calendar items and clicks the top link again then the Postpone-menuitem will receive both the IDs of the meetings already postponed and the new IDs. You can avoid this by using the execute component's special column
admin_unselectall to clear all checkboxes.
SQL for retrieving the resources for the calendar. All resources are displayed as dropdown resources on top of the calendar.
SQL for retrieving extra information for calendar days. The extra information is displayed directly below the calendar day headings. It is also possible to specify if a day is a holiday.
Sql for retrieving the calendar items to display in the calendar.
Called after every drag & drop operation.
Allows you to validate the parameters supplied by the user before any other SQL is run in the component. This call is only made if the component has visible parameters, the SQL is a stored procedure, and 'Validate parameters' is checked.
SQL that can have several resultsets that are displayed at top of component.
|LabelAbove||Full width, label above.|
|NoLabel||Full width, no label.|
|Standard||Label to the left.|
Use this call to restrict which entries a user is allowed to view and edit, and to log which entries a user views.
Access to a menu item is normally controlled through functions and roles alone but some entities need more fine grained control. For example, a user may have access to the View Member menu item for normal members but not for members with a protected identity.
The menu items a user visits are always logged (in ADMINLogMenuItem) but for sensitive data you may need to log exactly what entries are viewed. Do the logging in this call as the common ways of viewing data (grid and InfoSQL) are not allowed to modify the database.
If you bind a scalar function instead of a stored procedure to this call then its name must end with '_GrantAccess'.
CREATE OR ALTER PROCEDURE Example.Entity_Calendar @FromDate date = NULL, @ToDate date = NULL, @ExtraInfo bit = NULL, @Resources bit = NULL AS BEGIN IF @Resources = 1 BEGIN RETURN; END; IF @ExtraInfo = 1 BEGIN RETURN; END; SELECT CalendarDate, CalendarItemHeading, CalendarItemText FROM Example.CalendarItems; END;