M
Michiel de AutomateDoctor
When using Contracts with “Update custom fields with response”, we’re seeing that not all custom fields appear consistently in the mapping list.
Some fields show up correctly, while others don’t, even though they exist and are used elsewhere in the system.
Would be good to clarify:
  • if there are limitations based on field type
  • differences between system fields vs custom fields
  • or any best practices to ensure all needed fields are available
Clarifying this would help make Contracts more reliable across different use cases.