Dear all,
We have recently set up our Silverfin development environment and are currently working on further developing our statutory/judicial documents.
To ensure that our changes do not unintentionally affect existing documents, we have created several test dossiers that we use to verify that no critical changes have been introduced elsewhere.
As part of this process, we also need to add directors, shareholders, and other company stakeholders to these dossiers. Since we do not have a direct connection to our administrative environment in the development setup, we attempted to do this using the Get People of a Company and Update People of a Company APIs.
While we are able to create directors and shareholders through the API, we seem unable to use them effectively within our documents because they are not linked to a specific period. As a result, they do not appear to be available in the same way as period-related data.
For illustration ,the snippet above returns three 0 in this case.
Has anyone encountered a similar issue, or does anyone know of a recommended approach or solution for handling this in a development environment?
Thank you in advance for your help.
Hi @Maarten_Vandenhende!
Thanks for the detailed write up! This is a known limitation when working in a development environment with manually uploaded bookkeeping data.
The root cause:
period.people, period.directors and period.shareholders in Liquid templates are populated by the administrative sync (the connection to your accounting software). In a dossier without that connection, these collections are empty, even if people are visible in the UI. The Get/Update People of a Company API writes to the company-level people list (what you see in the UI) but not to the period-level collection that the Liquid reads from.
The recommended approach:
To use period.people, period.directors, and period.shareholders in your development environment, you need to push the people data via an admin sync. Importantly, this does not need to be a real admin connection, it just needs to be an active sync set up in the dossier. Once a sync is active, the yellow banner indicating that more recent data is available will appear in templates, and the period-level people data will be populated correctly. Once the yellow banner appears, trigger the sync, this is what actually pushes the people data into the registry.
Without any sync configured in the dossier, the period-level people collections remain empty regardless of what is added via the API, which is what you are currently experiencing.
Let me know if you run into any further issues!
Kind regards
Delphine
