Good Evening,

We've observed that the task.note field is consistently included in various payloads.

During unrelated (task) imports, the task.note appears in the error logs and import results.

It also shows up when updates are applied to tasks (update results) and when checking mx_u for usage activity, as it is present in every XML payload  (mx_u_07).

Despite confirming that neither FSM Default nor custom metadata has the task.note set to Force Select, and even after creating a custom column definition for task.note with Force Select explicitly set to "N", the issue persists.

Our problem with this is that task.note often contains extensive text related to job specifications, making it a substantial addition to every payload, usage record, import log, and update payload. This likely impacts performance. Also, the length and format of task.note complicates reading our import logs and is problematic to paste into Excel due to multiple line breaks.

Do you have any suggestions on how we can exclude task.note from all payloads, except where updates to the note are explicitly required? Or is there a policy reason why task.note is always included?

Thank you.