Script Last Modified: Track When Qlik Load Script Edits Happen
Many Qlik developers have asked for a separate "Script Last Modified" date, and the reason is simple: Qlik Sense gives an app one Last Modified timestamp, and it doesn't reliably reflect load-script edits. Someone can rewrite a whole section in the Data Load Editor, and from the hub the app looks untouched. When a reload breaks or a number shifts, you have no way to tell whether the script changed yesterday or three months ago — or who touched it.
How teams track script changes today
Without a script-level timestamp, teams improvise. Some paste a comment block at the top of the script — a hand-maintained changelog with initials and dates. Others keep a spreadsheet, or rely on the QMC audit log, which records that the app was modified but not what changed inside the script. The most careful teams export the .qvf before every edit and keep dated copies on a network share.
Gitoqlok brings Git version control, collaboration and change history to Qlik Sense and Power BI — right inside your browser. Try Gitoqlok Free
All of these drift. The comment header is only as honest as the last person who remembered to update it. The dated copies pile up until nobody knows which backup holds which version. And none of them answer the actual question during an incident: which line of the Main section changed, when, and by whom. You end up diffing two exported scripts by eye at the worst possible moment.
How Gitoqlok timestamps every script change
Gitoqlok versions the load script as real files in a Git repository: each script section becomes its own data_load_script/<section>.qvs file, alongside the section order and the full joined script. When you open the Gitoqlok popup on the Local Changes tab, it compares the current app with the last committed version and lists each changed section with a details link showing exactly what differs. You click Save changes, pick a message, and that commit records the author and the exact time — a true "script last modified" entry that Qlik never gave you.
To see history, turn on Qlik Helper and open the Diff Editor in the Data Load Editor: the current section sits on the left, any past commit on the right, differences highlighted line by line, with the commit dropdown labelling each version by author and timestamp. Every save is a dated, attributed restore point, so "when was this script edited, and by whom" becomes a glance at the timeline instead of a forensic exercise. See Load Script Diff for the full walkthrough.