Function Fields are leaving quite the paper trail?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-21-2023 01:47 PM
Hi all,
We've just recently been granted access to and started using Function Fields in reporting. However, our platform architect recently threw a flag on our usage after noticing that our function fields were modifying table structure by adding Dictionary Entries. Since we were using these in prod and not moving them up the stack this put prod out of sync with our lower environments.
He is proposing that we build these in dev and move them up the stack. I'll obviously follow his lead, but it feels like it kind of defeats the purpose of Function Fields. They seemed meant to empower us Report users to tweak the data delivery without bothering our developers.
Furthermore as I was deactivating some of what was in production, I'm noticing that dictionary entries are NOT deleting when a function field deactivates. I don't think he'll be thrilled to notice that.
Does all of this sound typical? How has it been handled in your SNOW environment? Thanks
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-21-2023 04:35 PM - edited 12-21-2023 04:36 PM
Hi @Jason D2
basically, your observations regarding function fields are correct. These fields are nothing else than real table extensions on the database level. And such changes should always be made on all instanes to make sure they behave similar.
Another option would be to clone the PROD over DEV and TEST regularly.
Maik