dataset

This is used to define discrete sets of data for scheduling. By default there is one dataset called Default. Where installations wish to schedule multiple sets of data as different scheduling problems then a separate dataset must be used for each.The dataset id only has to be specified as part of the Input_Reference and not included in the data for each entity input into the system.

Syntax:

[ DynamicComponentDependency ] dataset DatasetName {
[ TimeSpanUOM ] [ TimeZoneOverride ] [ ChangeDetection ] [ CustomChangeHandler ] #SqlDml.QueryBlock ;
}

Mandatory columns

Column Name	Data Type	Description
id	String(32)	Unique id for the data set.
dataset_type	String(32)	This is only for internal use and will be populated automatically.
last_update_datetime	Date	Used internally to indicate when there was last an update for this dataset.

Optional columns

Column Name	Data Type	Description	Default Value
organisation_id	Number	The organisation this dataset belongs to.	1
dataset_class	String(32)	This is only for internal use and will be populated automatically.	SCHEDULING
running_state	String(32)	This is used to control the processing of datatsets by the DSE for different types of operation.	NO_DATA
alias_id	String(100)	Internal identifier to be populated by applications when dataset_id is provided.
dataset_id	String(32)	The id of the parent dataset which must also be of dataset_type = 'COMPLETE'
description	String(2000)	Name and description.
external_id	String(80)	An external id for the dataset.
footprint	Double	An estimate of the size of the dataset as a scheduling problem.
process_type	String(32)	Identifies a particular process to be executed for this data.
profile_id	String(32)	The profile of the configuration parameters to use for the input set of reference data.



            dataset Dataset {{SelectName}} {
               SELECT
                     ..                  id,
                     ..                  dataset_type,
                     ..                  last_update_datetime,
                  -- optional columns
                     ..                  organisation_id,
                     ..                  dataset_class,
                     ..                  running_state,
                     ..                  alias_id,
                     ..                  dataset_id,
                     ..                  description,
                     ..                  external_id,
                     ..                  footprint,
                     ..                  process_type,
                     ..                  profile_id
               FROM {{sourceTableName}}
               WHERE ...;
            }

Note: All selected columns must have correct aliases that match a IFS Scheduling Dataset.

DatasetName

Syntax:

<Identifier>

This page is generated from IFS Developer Studio at 2021-08-13 08:48.