Currently custom fields on a CapsuleCRM contact only appears in Add Organisation task creation if marked ‘Both People & Organisation’
Some custom fields only make sense in Organisation, so having it appear in People entry is distracting.
Is there any reason custom fields need to be set to both types rather than just Organisation as intended?
Hi Perry,
Thanks for your message.
This arises due a discrepancy between how we see things in the Capsule Interface, and how the Capsule API allows us to interact with ‘Parties’.
In the API, we can deal with an object type of ‘party’ which can be a person or an organisation, rather than each individually.
I’ll reach out to Capsule to make sure we’re not missing anything here, as I agree it would make sense to limit the fields to the specific person or organisation type if we can 
Thanks,
Steven
Hi Steven or Perry,
Has there been any progress towards resolving this issue?
Thanks,
Kurt
I’ve also noticed that even if you create a custom field in Capsule configured to be used by both People and Organizations, and you create a ‘number’ field, it is seemingly not pulled by the Capsule connector in FlowXO.
Has anyone had this problem, and is it something that the flowxo team is aware of?
Hi @anderkd
It looks as though there’s still a problem for the add an organisation action where it doesn’t detect fields set to ‘Just for organisations’. I can also see the issue you mentioned regarding the number custom fields.
I’ve raised this with our dev team to have a look over the integration to see if there’s anything we can get out as a fix in a future update.
Just thought you’d like to know the issue for number fields and ‘just for organisation’ fields has now been resolved. Our dev team has put out a fix. 