# January 15, 2026 / šŸ‘® Validation rules, New Connector styles and options, ā€œPeriodsā€ integration **URL:** \ **Category:** Changelog\ **Created:** [January 15, 2026, 12:00pm UTC](https://community.fibery.io/t/january-15-2026-validation-rules-new-connector-styles-and-options-periods-integration/10247 "2026-01-15T12:00:31Z")\ **Posts on this page:** 14\ **Page:** 2
**Author:** ![grex22](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/grex22/32/10249_2.png) [@grex22](https://community.fibery.io/u/grex22)\ **Post date:** [January 16, 2026, 5:24pm UTC](https://community.fibery.io/t/january-15-2026-validation-rules-new-connector-styles-and-options-periods-integration/10247/22 "2026-01-16T17:24:07Z")
Validation is such a great feature that personally wasnā€™t on my radar, but now I wonder how I lived without it šŸ˜‚ Fibery team is hitting the ground running in 2026. Awesome stuff! ---
**Author:** ![Sppam\_Kontrol](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/sppam_kontrol/32/12112_2.png) [@Sppam\_Kontrol](https://community.fibery.io/u/Sppam_Kontrol)\ **Post date:** [January 18, 2026, 1:12am UTC](https://community.fibery.io/t/january-15-2026-validation-rules-new-connector-styles-and-options-periods-integration/10247/23 "2026-01-18T01:12:00Z")
we tried to do some testing on Periods twice. We were not sure how entity sync allocation works which is a bad thing from our side. We just tried like 2 period runs as how it was suggested from the period guide documentation, and hahaha we already went to a sync limit error. It would be nice if the team can provide the ā€œactual sync #ā€ when we try to create a new period sync. ---
**Author:** ![Chr1sG](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/chr1sg/32/3941_2.png) [@Chr1sG](https://community.fibery.io/u/Chr1sG)\ **Post date:** [January 18, 2026, 1:26am UTC](https://community.fibery.io/t/january-15-2026-validation-rules-new-connector-styles-and-options-periods-integration/10247/24 "2026-01-18T01:26:24Z")
> [@Sppam\_Kontrol](#): > > We just tried like 2 period runs as how it was suggested from the period guide documentation What options did you choose? > [@Sppam\_Kontrol](#): > > We were not sure how entity sync allocation works > **[Monthly usage caps for automations, integrations, and AI](https://the.fibery.io/@public/User_Guide/Guide/Monthly-usage-caps-for-automations,-integrations,-and-AI-384/anchor=Integrations--f0b6ada5-f9db-44b5-8990-711037348764)** > [@Sppam\_Kontrol](#): > > It would be nice if the team can provide the ā€œactual sync #ā€ when we try to create a new period sync You can check the sync config and it will tell you how many entities were synced on the most recent sync. > [@Sppam\_Kontrol](#): > > we already went to a sync limit error What plan are you on? If you sync all period types (days, weeks, months quarters, years) each year consists of fewer than 440 entities, so itā€™s hard to see how you can have used several thousand unless you synced many years, or did a force full sync many times. Do you have any other integrations active? ---
**Author:** ![nathan\_jay](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/nathan_jay/32/11899_2.png) [@nathan\_jay](https://community.fibery.io/u/nathan_jay)\ **Post date:** [January 20, 2026, 6:25am UTC](https://community.fibery.io/t/january-15-2026-validation-rules-new-connector-styles-and-options-periods-integration/10247/25 "2026-01-20T06:25:08Z")
Great update, starting the year off strong! > [@mdubakov](#): > > ## Validation rules > > Today weā€™re introducing new concept in Fibery ā€” Validation Rules. Yes!! I was talking about this earlier today with someone in my team because we had some invalid data šŸ™‚ This implementation keeps it wider but I would also like a narrower version for the ā€œAdvancedā€ settings of each Field so the validations can be targeted and in context. That might also give you an on ramp to Pro plans i.e. single field validation is standard but complex is Pro feature šŸ¤·ā€ā™‚ļø First thoughts (without testing): - Seems to be on DB level so is there a central place to manage my validation rules across the workspace? This will get out of control with sprawl much like the Access settings - What happens with API? I use it a lot so wondering how it handles invalid when using create or update? The default rule seems to be an ā€œupdateā€ trigger so the initial create over API can be done with invalid data? > [@mdubakov](#): > > - Access previous values of fields (it will enable validation use cases for state transitions). > - Access to a user who executes an action (it will enable validation use cases regarding user role or team). Canā€™t wait, and this will allow the validation rules around State field transitions so I can better mange workflows > [@mdubakov](#): > > Entity View: Quickly Show/Hide all fields I got annoyed about this just yesterday šŸ™‚ > [@mdubakov](#): > > Dates: ā€œPeriodsā€ integration Another mind read! I was trying to create a new report today. Iā€™ll check it out but I already know one caseā€¦for our Sales pipeline we estimate if a deal will close ā€œThis monthā€. And the Xero integration for our invoices > [@mdubakov](#): > > We may also reconsider double shift shortcut, since now it is causing problems šŸ™‚ Double shift shortcut is good for me FWIW ---
**Author:** ![mdubakov](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/mdubakov/32/10_2.png) [@mdubakov](https://community.fibery.io/u/mdubakov)\ **Post date:** [January 20, 2026, 7:41am UTC](https://community.fibery.io/t/january-15-2026-validation-rules-new-connector-styles-and-options-periods-integration/10247/26 "2026-01-20T07:41:07Z")
> [@nathan\_jay](#): > > What happens with API? I use it a lot so wondering how it handles invalid when using create or update? The default rule seems to be an ā€œupdateā€ trigger so the initial create over API can be done with invalid data? Since there is no Validation rules on Create, you can create whatever you want so far. If you Update via API, you will get an error if validation rule is violated ---
**Author:** ![timothy](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/timothy/32/11812_2.png) [@timothy](https://community.fibery.io/u/timothy)\ **Post date:** [January 20, 2026, 2:31pm UTC](https://community.fibery.io/t/january-15-2026-validation-rules-new-connector-styles-and-options-periods-integration/10247/27 "2026-01-20T14:31:57Z")
@nathan_jay Do you have a working Xero integration? Would you mind sharing? I built accounting into Fibery but my accounting team is after me to standardize around Xero because it more natively connects with so many financial data streams ā€¦ which is great, but Iā€™ve been dragging my heels on building the integration from scratch. Any pointers or template or anything youā€™d be willing to share? ---
**Author:** ![interr0bangr](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/interr0bangr/32/8089_2.png) [@interr0bangr](https://community.fibery.io/u/interr0bangr)\ **Post date:** [January 23, 2026, 1:37am UTC](https://community.fibery.io/t/january-15-2026-validation-rules-new-connector-styles-and-options-periods-integration/10247/28 "2026-01-23T01:37:36Z")
Will the validation trigger of ā€œEntity Createdā€ or ā€œEntity Creation Attemptedā€ be coming soon? My use case would be I donā€™t want let users be able to create a new ā€œgoalā€ that is linked to a ā€œquarterā€ if the goal being created isnā€™t also linked to a parent goal. (goals have a 1 to many self relationship). But if a goal is created without being linked to a quarter, that should be allowed. I could have a regular rule do this, but it would create and then delete the offending goal and would confuse users. I want to restrict the goal from being created in the first place and inform the user why it didnā€™t meet the criteria. ---
**Author:** ![mdubakov](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/mdubakov/32/10_2.png) [@mdubakov](https://community.fibery.io/u/mdubakov)\ **Post date:** [January 23, 2026, 9:23am UTC](https://community.fibery.io/t/january-15-2026-validation-rules-new-connector-styles-and-options-periods-integration/10247/29 "2026-01-23T09:23:21Z")
We will collect more feedback before adding new events. I hope we will get back to it in several months. ---
**Author:** ![nathan\_jay](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/nathan_jay/32/11899_2.png) [@nathan\_jay](https://community.fibery.io/u/nathan_jay)\ **Post date:** [January 27, 2026, 10:16am UTC](https://community.fibery.io/t/january-15-2026-validation-rules-new-connector-styles-and-options-periods-integration/10247/30 "2026-01-27T10:16:01Z")
@timothy sorry I may have given you false hope using ā€œintegrationā€ word but Iā€™m happy to help I originally had an import script. And I just finally made a custom integration (more below). The script was JS on Google Apps Scripts which runs a daily import to Fibery. It is only importing invoices (ACCREC) (with only limited data about amount, status, etc) and some related Contact information. I then worked on a proper Custom Integration and only just now deployed it working. I used the exact method from the Fibery team AI Custom Integrations. I commented here about how well it works on my first attempt and it still applies šŸ‘‰[šŸ¦„ Custom Fibery Integration Development with AI - #11 by mdubakov](https://community.fibery.io/t/custom-fibery-integration-development-with-ai/10151/11). However the integration is the exact same limited scope as the script. But one thing I did was I spent sooooooo long on getting the OAuth to work. In fact that was the only real bug. Iā€™m sure a real developer could have isolated the issue faster and more programatically tested. But it seems to be some quirks with how Xero works with multi-tenants and some comments in the Fibery documentation, and I have no idea what Iā€™m doing šŸ™‚ Below are some rambling tips. I sure Iā€™m telling you things you already know generally about software dev as well: - I used Claude for everything. You may not need it but Opus 4.5 because I have Max plan so why not. - Plan phase output to an md file so I could read more deeply and make specific manual edits to the plan - Itā€™s really limited in scope compared to the breadth of the Xero API docs so that helped to keep it focused. Only 2 DBs with Invoices and Contact both with limited fields. - I donā€™t know how but you should have very verbose logging on the OAuth to include all steps in the chain. I spent a lot of time with piecemeal changes and re-test, fail, analyse the logs. - The new MCP tool for Claude will help to read the Fibery user guide. I forgot it was released last week and it may have saved some time. I could have worked around to get the help docs in but to be honest I just forgot. - I didnā€™t realise until later that the free tier Vercel only streams logs (canā€™t query after) for up to 5 mins so I was wasting time in this loop. Basically, if you can give LLM direct access to query the logs then the debug loop will be much shorter. Or just pay and donā€™t be cheap šŸ˜† I hope that helps! And Iā€™m happy to share more if I missed something. ---
**Author:** ![nathan\_jay](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/nathan_jay/32/11899_2.png) [@nathan\_jay](https://community.fibery.io/u/nathan_jay)\ **Post date:** [January 30, 2026, 5:58am UTC](https://community.fibery.io/t/january-15-2026-validation-rules-new-connector-styles-and-options-periods-integration/10247/31 "2026-01-30T05:58:00Z")
> [@danielbmarsh](#): > > **UI Enhancement to Fields** > Validation rules (and other rules) should be visible in the settings of the fields they reference. Exactly! I know it could exist in the general Validation Rules but to me it belongs on the Field settings so itā€™s visible when creating a new field, and then after the fact I know where to find it. The UI can be simplified but you get the idea: ![image](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/f/f71033a877e1003984df6b6751d3bbce1df0f508.png) Ideally it would also display a link to any other Validation Rule which touches this field. Hubspot has similar UI where they display ā€œUsageā€. This is pretty dense but basically for any property (field) you can can see a list of where its used, or in this case, which Validation Rules touch it. ![image](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/c/ce86d2946e78eb5aba528cad6203481510bec8e4.png) ---
**Author:** ![Minh\_Tri\_Do\_Hang](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/minh_tri_do_hang/32/6791_2.png) [@Minh\_Tri\_Do\_Hang](https://community.fibery.io/u/Minh_Tri_Do_Hang)\ **Post date:** [February 4, 2026, 2:04am UTC](https://community.fibery.io/t/january-15-2026-validation-rules-new-connector-styles-and-options-periods-integration/10247/32 "2026-02-04T02:04:31Z")
> [@mdubakov](#): > > Dates: ā€œPeriodsā€ integration Iā€™m one of the very first users of this Period database. @Chr1sG Right now the old version is acting up ā€” it keeps throwing errors and doesnā€™t sync continuously. ![image](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/3/3fbcd4091bd3ce976fe4c3d83738fa09b4a177b4.png) I really donā€™t want to switch to the new ā€œPeriod Integrateā€ template because Iā€™ve heavily customized the old one: tons of custom fields, relations to many other databases, automations, rules, and a bunch of extra views. Is there any way to update the old database to the new version while keeping everything exactly the same, without breaking anything? ---
**Author:** ![Chr1sG](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/chr1sg/32/3941_2.png) [@Chr1sG](https://community.fibery.io/u/Chr1sG)\ **Post date:** [February 4, 2026, 7:04am UTC](https://community.fibery.io/t/january-15-2026-validation-rules-new-connector-styles-and-options-periods-integration/10247/33 "2026-02-04T07:04:11Z")
Iā€™m afraid itā€™s not possible to migrate a custom integration to a native integration, and the experimental version is no longer supported. ---
**Author:** ![Minh\_Tri\_Do\_Hang](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/minh_tri_do_hang/32/6791_2.png) [@Minh\_Tri\_Do\_Hang](https://community.fibery.io/u/Minh_Tri_Do_Hang)\ **Post date:** [February 6, 2026, 4:57am UTC](https://community.fibery.io/t/january-15-2026-validation-rules-new-connector-styles-and-options-periods-integration/10247/34 "2026-02-06T04:57:28Z")
Is there a way to set a daily template for the period/entry? For example, every day I want it to automatically show up in a format that mentions multiple topics and all the projects Iā€™m currently working on. ---
**Author:** ![Chr1sG](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/chr1sg/32/3941_2.png) [@Chr1sG](https://community.fibery.io/u/Chr1sG)\ **Post date:** [February 7, 2026, 12:30am UTC](https://community.fibery.io/t/january-15-2026-validation-rules-new-connector-styles-and-options-periods-integration/10247/35 "2026-02-07T00:30:46Z")
Do you mean that you want to populate a rich text field, attached to the Day entities in the Period db, with a summary of topics/projects that are currently active? [Previous page](https://community.fibery.io/t/january-15-2026-validation-rules-new-connector-styles-and-options-periods-integration/10247.md?page=1)