Summer is here, and the community has been buzzing with great questions and answers.
This month we're highlighting some topics that came up recently.
Let's go 👇
🔧 The Use Of 'period.people'
If you're working in a Silverfin development environment and notice that period.people, period.directors, or period.shareholders are empty even after adding people via the API, you're not alone. This came up in the community this month and the answer is an important one to know.
The root cause: these collections are populated by the administrative sync (the connection to your accounting software). In a file without that sync configured, the period-level people data remains empty even if people are visible in the UI. The Get/Update People of a Company API writes to the company-level people list, not to the period-level collection that Liquid reads from.
The fix: you need to have an active admin sync set up in the file (it doesn't need to be a real connection). Once a sync is active, a yellow banner will appear in templates indicating more recent data is available. Triggering that sync is what actually pushes people data into the period registry.
A question came in about using a reconciliation result (e.g. reconciliations.some_template.results.some_result) in a report, where the reconciliation doesn't exist for newer companies. Using default: 0 directly in the report formula causes problems, it overrides the value even for companies where the reconciliation does exist.
The fix: rather than adding the default in the report, add it at the source inside the some_template reconciliation template where the result is defined. That way the result always has a numeric value regardless of whether the template is in use, and the report formula stays clean.
A question came in about whether it's possible to have one page per annex or title in a PDF export. The short answer is yes, and here's how it works.
Page breaks in Silverfin are controlled through the style settings of the export bundle. Within the export configuration, you can specify that each section or annex starts on a new page.
If you're using a custom style bundle, you have two options: adjust the Liquid code in the style directly (via Styles → Modify Styles), or create separate blocks in the export settings, each block will print page by page with its own title. For complex style changes, reach out to Customer Support
We've expanded the signmarker tag with new attributes. If you're using digital signing integrations in your templates, here's what's now available:
The tag already supported name and email. You can now also pass phone, role, and on_behalf_of giving signing integrations more context about each signature.
Keep in mind: each attribute can only be used once per tag, and you'll need one signmarker per signature (combine with a for loop when multiple signatures come from a collection). Also make sure your signmarkers are never placed inside input comment tags (they won't be exported to PDF if they are).
