SharePoint List Writer

This node writes a KNIME table to a SharePoint list.

Notes:

• Writing tables with more than a few hundred rows can take long time. Overwriting an existing table can be also very slow in case a lot of rows need to be deleted.
• When appending data to an existing list, the name of the input table columns are matched to the display names of the respective columns in the SharePoint list. In this process read-only columns are ignored. If multiple list columns have the same display name, the first will be chosen. The node will fail if there is no list column matching a specific table column or if a required list column is not present in the input table. Any list columns which are not present in the table will be populated with their default value by SharePoint.
  This node will not perform any type checking when appending values.
• The default "Title" column of the list (which may have a different display name) is used by this node to store the RowID. Use a RowID node to specify a custom one. If a column with the same name is already present in the input table, it will be mapped to a (new) column with the same display name.
• If an input table contains columns whose name are already used by read-only system columns, the node will create new writable list columns of the same name when creating a new list or overwriting an existing one.
• This node exports the ID of the written list to a flow variable called sharepoint_list_id. The ID can be used in subsequent nodes to control the listId setting via flow variable.

KNIME column type support

Fully supported KNIME column types:

• String and string-compatible columns map to Multiple lines of text
• Integer columns map to Number
• Boolean columns map to Yes/no

Partially supported KNIME columns types:

• Long columns map to Number . The node will fail for more than 15 significant digits (digits which remain after leading and trailing zeros are removed, i.e. in "401220500000" the digits "4012205" are significant and in "0.0004050114" the digits "4050114" are significant).
• Double columns map to Number . The node will fail for infinity, NaN and values outside of [1.79E308,-1.79E308], as well as for numbers with more than 15 significant digits.
• Local Date and Local Date Time columns map to Date and Time , which stores a UTC timestamp with second-precision. Hence, values from KNIME are mapped to an instant in UTC and truncated to second-precision. For example, 2022-02-02 08:00:00 is stored as 2022-02-02 08:00:00 UTC. The node will fail for values before 1900-01-01 00:00:00 UTC and after 8900-12-31 23:59:59 UTC.
• Zoned Date Time columns map to Date and Time , which stores a UTC timestamp with second-precision. Hence, Zoned Date Time values are converted to the UTC timezone and truncated to second-precision. For example, 2022-02-02 08:00:00 CET is stored as 2022-02-02 07:00:00 UTC. The node will fail for values before 1900-01-01 00:00:00 UTC and after 8900-12-31 23:59:59 UTC.

Unsupported KNIME column types:
All column types that do not belong to the above categories are unsupported and the node cannot be executed, since there is no corresponding type in SharePoint.