Skip to main content
Question

Writing null/blank values to SharePoint Online

  • Sep 30, 2026 3:11 PM UTC
  • 1 reply
  • 64 views

phoeffler
Supporter
Forum|alt.badge.img+13

I have a workspace using a ChangeDetector to maintain data in a SharePoint Online list, using a Microsoft SharePoint Server List writer (we are blocked from using the Graph API, so the Microsoft SharePoint Online List reader/writer are not options for us).

When a value has been written to a field in the list but is later removed in the source/revised data, the ChangeDetector recognizes this and sends either a null or blank/empty value to the writer, without error. 

But, the null/empty/blank value is not actually written or accepted, and the stale value persists.

I’ve found that if I use a NullAttributeMapper and map Empty, Missing, and Null values to a New Value and set that to a single space character, that SharePoint actually writes the null/blank value over the existing value. For anyone trying to do the same, this might be an important point.

The issue that I’ve run into is that Date/DateTime-type fields will not accept a space as input. I’ve tried writing in 00000000 and it is also rejected. I gave an FME DateTime-related function invalid parameters so that it produced a null value, but of course that did not work either.

Any thoughts on how to overwrite an existing value in a Date/Time field in a SharePoint list to a null/blank/empty value?

The work-around is to go and delete the value manually in the 365 web interface, but that is not ideal.

Appreciate any input on possible solutions.

1 reply

crystalwang
Safer
Forum|alt.badge.img+31
  • Safer
  • Nov 16, 2026 11:55 PM UTC

​Hi ​@phoeffler,

Thank you for posting your question on the FME Community, and for sharing your findings!

The behaviour you're seeing with the Microsoft SharePoint Server List writer appears to be a limitation of the writer when updating existing Date/Time fields with null values. This is an issue we're aware of and are tracking internally as FMEENGINE-77099. Unfortunately, we don't have a timeline for when a fix might be available.

In some workflows, using Drop and Create to recreate the list may be an alternative, although I understand this might not be practical for your use case.

In the meantime, one potential workaround you could explore is using the HTTPCaller to clear the Date/Time fields through SharePoint's REST API. This may be an option depending on your organization's restrictions.

While we haven't tested this approach for your specific workflow, the general idea would be to use the HTTPCaller to send an update request to the relevant SharePoint list item, setting the Date/Time column to a JSON null value.

Here are some resources that may help you get started:

Please let us know if you're able to try either approach or find another workaround that works for your workflow!