This field is required.
Only these extensions are allowed(.jpg, .JPG, .jpeg, .JPEG, .gif, .GIF, .png, .PNG)
Tags cannot contain the characters ' /, \\, #, ?, or ; >,< '
Only these extensions are allowed(.zip,.ZIP,.pdf,.PDF,.qvf,.QVF,.qvw,.QVW)
Discussion Board for collaboration related to QlikView App Development.
We are working on migration of qlikview documents from single server to clustered environment.
As a part of this effort, we are renaming the existing qlikview documents and going to follow a standard hereafter.
For example if the dashboard name is Readmission, we are trying to rename this as <Organization_Name>_<Department using this dashboard>_Readmission. This is one example.
Can some one suggest some naming standards like this practiced in your organization? It would be useful for us to implement a standard.
Maybe it makes sense to add the version number and last modification date of the document?
we use to follow below standards (in production) check once
Personally we keep our documents named friendly for our end users, things like this we store in the start of the script as version control.
The organisation_name & departments are not necessary as we have an NTFS folder & ad access setup on top of them so only the right people see the right dashboards.
we are currently using file name format like:
Organisation name is not required if file is accessed within organisation and in Date or Version only one is applicable because versions can't release on daily basis.
Please remember to mark this as "helpful" & "correct answer" if your are satisfied.
This will help users identify the answers should they come across this thread in the future.