The custom variables you have created are on the company drop. This means that the value of these input fields will remain the same throughout all periods. If you’ld like to clear these fields, attaching it to the company drop is not the right approach.
More information on company and period drops can be found in this case.
Is there a way, to use company.custom for some fields and also those fields can be made nil when roll forward?
We are using company.custom. in the liquid code to check the updates in the data fields and trigger the webhook events. Perhaps when we don’t use company.custom, we don’t see any webhook events for those fields.
Variables created at company level are not period dependent (i.e. they keep the same value regardless of the period you are in). For this reason, the rollforward functionality does not work for them.
Is there a reason why you need to use a company variable?
We have integrated Silverfin to the different applications and we are using Webhooks to trigger the events. Sense, whenever some custom data fields are updated in the Silverfin work papers, API is triggered to take
those updated data and will do necessary action on our other applications.
Silverfin only has webhooks for when a company custom property is updated on a company. i.e
{% input company.custom.namespace.key %}
Not for custom properties like.
{% input custom.namespace.key %}
So we are using Company custom properties, however we cannot make the fields nil when we roll forward to next year. This indeed triggers the API for next year data fields, when rolled forward, even when the user does not update the fields.
Is there a way to make these fields as period dependent and nil when rolled forward for the company custom properties fields?