You're welcome :)

Hi @lewerim - the method I showed to load Plasmic is unique to Plasmic, unfortunately. There may be a way to embed a SharePoint report into Knack but I'm not familiar with it so am not sure.

@@enlivenit I thought maybe it was. Thanks for the response.

Hah! Yes not light watching for 7am! Let me know if you try it out.

@@shofixti thanks for the lovely words. I agree there's operational considerations especially Make operation consumption. In reality, I would normally do some sort of (usually informal) risk management process to decide whether I need to bother going to the extra effort of protecting the endpoint. In many cases, I decide it is worth doing, but sometimes I'm happy to accept the small risk of someone unauthorised triggering a scenario to save on make credits and to keep it simple.

What do you usually do to gracefully handle API errors and timeouts?

@@enlivenit "Graceful" is relative, but we've generally used Break (retry) modules plus error handlers attached to all Knack operations (be they Knack modules or HTTP modules that do Knack things) just because the Knack API occasionally goes out to lunch. It's gotten better in the last couple years, but the number of failed calls is far from zero. Unfortunately this creates a clunky UI when users are watching a spinner for 2, 3, 5, or more minutes while Knack is getting its API ducks in a row and Make scenarios are re-running. "Just reload" is something of a mantra. As far as saving Make operations, it's more complex than just keeping everything in Make, but with a little know-how, I'd imagine it wouldn't be too hard to write an AWS Lambda function that does the session and token validation, and just call that at the start of any Make scenario that does Knack Stuff.

@@shofixti thanks - that's about what I would have expected within Make and what I've seen others do. What I do: I actually normally use Pipedream instead of Make for automation. I have written some pipedream components (a component is the equivalent of a Make "Knack" step) that are powered by my knack-api-helper package (www.npmjs.com/package/knack-api-helper plus see kzbin.info/www/bejne/hmSyg6FjpLKMba8). The advantage is that because these are powered by knack-api-helper they automatically retry failed API calls when sensible. This means that when those not-so-occasional Knack API glitches occur, a retry will happen almost immediately rather than relying on a delayed retry within Make or similar. I've found this to be very reliable due to the auto-retry, dramatically lowering error rates even when running 1000s of API calls. Because Pipeream allows defining custom components (workflow steps) I also have a component that validates a Knack session. This becomes just another step you can insert into a workflow and re-use wherever needed, avoiding the need to split into another Make workflow to run reusable logic. Certainly, you could write a Lambda function that can be called in place of the Make workflow to validate a Knack session and that would save some Make credits. I usually write Lambda functions within a Netlify project because it's so easy to write & deploy functions that way, rather than working directly with AWS, but whatever method you're comfortable with will work, of course. Once again, knack-api-helper can help if you were creating a lambda function - you could import knack-api-helper into the function then use the validateSession method to check the user is a logged in user of a particular role (github.com/CallumBoase/knack-api-helper?tab=readme-ov-file#validating-a-user-token---validatesession) which would save you writing the logic from scratch. If you'd like any more help or advice streamlining things further with AWS functions, or seeing how Pipedream looks as an alternative to Make, feel free to get in touch

Do you mean in the knack app JavaScript area? It's probably possible but knack is built on jQuery (if you inspect the source code sent by knack it's used widely) so I doubt theres any actual security benefits from avoiding using it in the knack JavaScript area code that you write.

Let us know how you get on and if you hit any roadblocks.

Thanks for the kind words Carl :)

Thanks! I'm glad you found it helpful. Do you have any other topics you'd like to see videos about?

Thanks Carl!

Glad you found it helpful! The 0 record trick is actually much more secure too - because a view hidden with js is simply hiding it from view, but it's underlying data is still available via the API very easily. However if you actually set data source filters or 0-record settings like shown in the video, that data is completely unavailable even if someone tried to get it via the api

Let me know how you go! Can you tell me more about your use-case for identifying parent and child pages? Might make a video on that, but need a little more context on what you're trying achieve with that

@@enlivenit I was thinking almost a site map, in tabular form. Not sure how useful that would be though, on second thought...

@@enlivenit Now I'm thinking it would be useful to have a catalog of Views and what Scene they are hosted on. 🤔 It's always inspiring to see what other people are working on....

@@lewerim Does find.knack.com/definitions#home/ serve that purpose for you of seeing a catalog of views and what scene they are hosted on? I have a video on how to use it here: kzbin.info/www/bejne/oXjbm6iFZbloq80 If not, I'm curious to know what else the catalog you're thinking of would do (and happy to make a video trying to address that need)

@@enlivenit it does. I use it regularly. I was really just thinking of what are the possibilities.

Glad you found it helpful! What are you working on in Knack @deborahpattie4570 ? Any other sticking points you'd like to see info about?

Thanks @lewerim. I agree that Knack docs don't explain it super well - it's one of those things that you intuitively pick up once you've built a lot, but it's not so intuitive when you first build. I like that way of thinking about child pages. Thanks for sharing.

No worries. Let me know how you go!

Thanks Martin for the feedback! Yes, I speak to lots of Knack users / clients who have set their app up with fields in child user roles and then later need to refactor. Much better to start that way first.

Thanks!

Thanks Martin! Yes, it's very powerful integrating Knack with other services

Thanks Carl!

Thanks @DataTechniques. I'm fascinated how you manage to jump into client's apps without it. Do you have some other magic methods for not breaking apps when you make changes?

Hi Jonathan, Thanks for your comment. 1) Yes, Knack could certainly be used in your scenario - to create the database of people for the directory with users being able to update their own profiles with login protected forms etc - it's exactly what Knack is designed for and would do it really well. 2) The integration is achieved via squarespace code blocks & header code injections combined and the Knack api. Some resources to get you started: docs.knack.com/docs/introduction-to-the-api support.squarespace.com/hc/en-us/articles/206543167-Code-Blocks It's a pretty involved little project, so I don't have any plans to make an extensive video tutorial on how to achieve the integration. Feel free to contact me through my business if you need more help - Enliven IT (enliven-it.com.au/). I offer coaching / training in Knack and the Knack API and also offer this integration as a product (the existing code library I've developed for the above video can adapted to other Knack apps and Squarespace websites, saving time and making it quite cost-effective for clients). If you were interested in working with me, I could create the whole integration for you - including building the Knack app, or we could work together and do the appropriate parts each, or I could just license the code library to you for a single app, if you want to adapt it yourself - I'm flexible about the exact arrangement, so feel free to get in touch. Kind Regards, Callum Boase

​@@callumboase3021 Thanks so much for your quick reply Callum! This is definitely helpful. The main question that I have now is whether or not you think the user would be able to filter on multiple levels. For example, if the Knack database includes a person's name, state, city, price, industry, and years of experience for each entry, could the user (in the website created by SquareSpace) filter for people who are in Texas, cost between $50-100, in the tech industry, and have 5-10 years of experience? That's definitely a key requirement for this project. If you know/think this could be implemented, I'd definitely be interested in working with you!