top of page

Connected Records Workaround with a Knack Database

Updated: Jun 23

Enhancing App Functionality: Overcoming Limitations

Hey there, Dave Parrish here! Today, I want to share an interesting workaround I discovered while developing an app that tracks the journey of medical devices through various facilities. It's been a bit of a journey itself, navigating through some unexpected hurdles, but I'm excited to show you how I overcame them.

The Challenge of User-Specific Data Display

I recently encountered an issue where I needed to display records in my app based not only on their relationship to a main object but also on the logged-in user's associated site. This proved trickier than expected with the tools I was using, namely Knack.

Expectations vs. Reality

Initially, I assumed Knack would seamlessly filter records based on the user's site when viewing detailed records. For instance, when coordinators logged in, they should only see devices associated with their assigned site within a specific study. However, Knack's default functionalities fell short of this requirement.

Finding a Solution with Support

After some back-and-forth with Knack's tech support, I learned about a workaround that, while not perfect, significantly improved the user experience and functionality of the app.

Implementing the Workaround

Let me walk you through how I implemented this workaround step-by-step:

Understanding the Setup

  1. App Overview: My app tracks medical devices across different sites for compliance purposes.

  2. Coordinator Access: Coordinators log in to view studies assigned to them and devices associated with their site.

Step-by-Step Implementation

  1. Customizing Views: Instead of relying on Knack's default grid view, I switched to a search view. This allowed me to add specific search criteria, crucially filtering devices based on the logged-in user's site.

  2. Setting Search Criteria: I configured the search view to only display devices associated with the site of the logged-in user. This was achieved through setting up a custom search filter that limited selectable options to the user's associated sites.

  3. User Experience Enhancement: To streamline the process further, I implemented a small piece of code that automatically triggers the search when the page loads. This minor tweak eliminated the need for coordinators to manually initiate the search, making the interface more intuitive and user-friendly.


The workaround proved effective in achieving the desired functionality, albeit with some initial setup and minor coding adjustments. Now, coordinators can seamlessly navigate through studies and see only those devices relevant to their site, enhancing both efficiency and user satisfaction.


Navigating through challenges in app development often leads to unexpected solutions that significantly enhance functionality and user experience. While my journey with Knack presented its challenges, it ultimately reinforced the importance of perseverance and creative problem-solving in software development.

I hope this walkthrough of my experience was insightful and helpful for your own projects. If you've encountered similar challenges or have alternative solutions, I'd love to hear about them! Feel free to share your thoughts and experiences in the comments below.

Thanks for joining me on this journey of overcoming app development hurdles. Until next time, happy coding!

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

16 views0 comments


bottom of page