What happened
What this says
Current to 11 Oct 26Paul asked how to export records with derived fields tracking duplicate repairs. Olivia explained the fields are stored in Snowflake tables and can be exported from there with IT support.
Problem: Paul needed to export records with derived fields created in the brain to track repairs counted twice. Handling: Olivia clarified that derived fields live in Snowflake tables and can be queried or exported from there, requiring IT collaboration. The ticket shows successful user adoption of the platform architecture.
Details
Updated 9 Oct 26Prioritynormal
Statusclosed
Categoryhow_to
Channelemail
First response (min)366
Helpdeskmade from
Trail
- created · Paul Rigby 22 May 2026 13:23Hi, following on from our last chat about dashboards, I've got another question about getting data out. We're building some derived fields in the brain to track repairs that have been counted twice, and I need to export those records with the new fields back to the system. Is there a way to do that, or do I need to handle it in Snowflake? Any pointers would help.
- public_reply · Olivia Grant 22 May 2026 19:29Hi Paul, I've seen your earlier ticket about dashboards. Good question about derived data. The brain runs inside your Snowflake, so the derived fields you create are actually sitting in Snowflake tables. You can export them or push them back to your source systems from Snowflake, but you'd need to work with a colleague in your data or IT team on that side. Happy to point you to the right documentation or we could do a quick call if that would help?
- public_reply · Paul Rigby 26 May 2026 10:49That's helpful, I didn't realise the fields were already in Snowflake. So the brain is writing them there as I create them? If that's the case I can probably sort the export myself. Just to confirm, if I create a derived field in the brain UI, does that go straight into a table in Snowflake that I can query?
- status_change · 9 Jun 2026 23:59
Helpdeskmade from