Awesome new KTL feature, looking forward to trying it out. Being able to see a concise record history just detailing what has changed is a real game changer. I have had so many requests over the years for a simple way of seeing who changed what and when. Thank you
Love the work on KTL! unfortunately its due to the lack of product development by knack themselves. I know that there has been a lot promised but nothing meaningful yet
I understand your frustration with the slower rate of change in new features. The new team has faced significant challenges with the legacy architecture, which has impacted their progress. However, I am aware that substantial efforts are being put into developing the new builder and live app. These updates will leverage more modern and updated code libraries, enabling new features to be rolled out more efficiently.
I am a strong advocate of KTL and am continually impressed by what @NormandDefayette_CortexRD has achieved and continues to develop.
Knack remains an exceptional platform for building a wide range of applications. While progress may not match the pace of larger companies, the smaller, niche nature of Knack is a major reason why I appreciate the company and the platform.
Thanks Norm… that was a typo, I have copied the keywords from the guide and used _vrh and used this _vrh=[Hist, fa-clock-o], [filters, Developer, Administrator], [align, center] but it doesnt appear! I will have a look at Carl’s video below and see what I have missed.
Thanks for this tool. As a new user I was shocked to discover this wasn’t native functionality.
Can someone elaborate on how and why an API call is used every time this occurs?
Is there a way to manage this without triggering an API call? If it involves extra steps (e.g. configuring some record actions or tasks or something) I’m ok with it.
Using API calls is the only way you can have a remote form view (that is not part of the current page you’re on) to submit data using Javascript.
This form becomes the “single point of entry” for all places you want record history.
There is no other way to do it, not even with record rules or anything I can imagine.
I guess you’re on the Starter plan, since you seem to be pretty concerned with API calls?
Remember that you can fine-tune your usage by limiting the amount of record history to only specific forms or account roles.
I’ll admit I was very green when I posted this and with a week under the belt I now have a better understanding of things and it makes more sense how this is actually working.
Thank you for your work with KTL tools, without this specific solution (and there being no native front-end record history) we would have been looking at using another platform.
The Knack team are lucky to have you supporting their community.
Hey Normand! Thank you SO much! KTL is a true GAME CHANGER!! I set up Record History, and I am getting history, but the Identifier field is not populating, and the History URL is not showing anything, even though I should be on a plan that has that. Here’s a short video: Record history question | Loom Any thoughts on how to fix that?
First of all, check if you have the Record History enabled in your app. You did the right test by checking directly in the Builder’s record history. If you have nothing there, the KTL feature will only follow since it’s the same link.
About the blank Identifier field, I’d have to recreate your use case. It could be due to that funky field name. A Text Formula is usually not a problem since I use them all the time as Display Fields.
Have you tried Rec Hist with something else to see if this one is an isolated case? Or change the field name for something basic maybe?
I’ll get back to you soon.
Request: Can you create a GitHub issue please so I can keep a track of that, and others can see it too?
Hey Normand! I have enabled record history, so the History URL is now working…thank you! I deleted the Identifier field and recreated it, but now that column is no showing up at all (before it was just blank). Here’s a short video: Normand follow up | Loom and I’ll create a Github issue. Thank you again…KTL is AMAZING!
10 Minutes
