top of page

Connect Products to Products to Make Kits in Knack

Updated: May 12

Interested in my Knack database services? ... Book a call with me here:

Hey there, it's me again, coming at you with another blog post.

So, picture this: I'm knee-deep in developing a Knack database app, still in its rough stages, but every interesting tidbit that pops up along the way, I just have to share. Today, it's about a fireworks company I'm working with. They've got a plethora of products—think sparklers, cracker jacks, things that light up the night sky. But here's the twist: sometimes they bundle these products into kits.

Now, you might wonder, why bother structuring it this way? Well, let me walk you through it. It's like organizing an invoice. You have a parent record, which is the kit itself, and then you have child records, each representing a product within that kit. It's all about making sure everything fits seamlessly together, like the perfect fireworks display on a summer night.

But, as with any project, there are hurdles to overcome. We need to clean up the data, differentiate between kit and non-kit products, and ensure that users can't accidentally add a kit within another kit. It's a delicate dance of structuring and organizing, but oh-so-important for smooth functionality.

One of the neat tricks we've implemented is Knack's automated calculations. You see, these kits come with various components, each with its own specifications. From the number of sparklers to the shots they produce, everything needs to be accounted for. So, we've set up formulas to tally up the totals automatically, saving users the headache of manual calculations.

But what about updates and changes? Well, we've got that covered too. Products can be deactivated or replaced over time, so we've built in features to track these changes and maintain a comprehensive history of each kit. It's all about keeping things up-to-date and audit-ready.

Now, let's talk about the nitty-gritty of how it's all structured. We have our main product table, housing all individual items. Then, there's a separate table specifically for kit products, where each item is linked back to its parent kit. It's like building blocks, each piece fitting snugly into place.

And here's the kicker: to make it all work seamlessly, we need not one, but two connections to the product table. One links the kit to its parent record, while the other allows for the selection of individual products to be included in the kit. It's a bit of a dance, but once you get the steps down, it flows like poetry.

Of course, there are always quirks to iron out along the way. For non-kit products, we manually input details like shots. But for kits, we've set up clever calculations to handle this automatically. It's all about finding that balance between manual control and automated efficiency.

So, there you have it—a glimpse into the inner workings of structuring product data and creating kits in a Knack database app. Until next time, stay curious and keep creating Knack apps. Cheers!

8 views0 comments


bottom of page