This defines a special day within a calendar where the usual availability pattern does not apply. The relative day number determines the actual date of the special day. The 1st January 2000 is counted as 1, and days count forwards from there. Thus the 2nd January 2000 would be 2, the 1st February 2000 would be 32, and the 1st January 2001 would be 367.
Syntax:
[ DynamicComponentDependency ] specialday SpecialDayName {
[ TimeSpanUOM ] [ TimeZoneOverride ] [ ChangeDetection ] [ CustomChangeHandler ] #SqlDml.QueryBlock ;
}
Column Name | Data Type | Description | Default Value |
---|---|---|---|
calendar_id | String(32) | Specifies the id of the calendar this relates to. | |
relative_day_number | Number | Specifies the day this relates to, counting from 1st Jan 2000 = 1. | |
description | String(2000) | Provides a description for this special day. |
Column Name | Data Type | Description | Default Value |
---|---|---|---|
is_working_day | Number (0 = False, 1 = True) | Indicates whether there is any availability on this day. | False |
specialday SpecialDay {{SelectName}} { SELECT .. calendar_id, .. relative_day_number, .. description, -- optional columns .. is_working_day FROM {{sourceTableName}} WHERE ...; }
Note: All selected columns must have correct aliases that match a IFS Scheduling SpecialDay.
Syntax:
<Identifier>
This page is generated from IFS Developer Studio at 2021-08-13 08:49.