qlikdeploymentframework / qlik-deployment-framework Goto Github PK

Hi @QlikDeploymentFramework we are wondering to know when do you plan to release the new version with bugfix for November2018

I´ve made some changes on LoadAll.qvs in order to initialize with QDF a bunch of custom and shared libraries. I save that changed file in Administration Container and ContainerTemplate hoping that file will be consider as default and every new container, the QDF will use that custom file. But Is not what really happen.

Every time a create a new container, the old version of LoadAll is replacing in all container.

I find that there are some confusion regarding bug fixes and versions.

QDF version 1.7.2 has been the last release for a while, but there has been made 7 commits to the master since May 24th, some of them are very important bug fixes for Qlik Sense November 2018. I see troubled users that could have been helped it they grabbed the latest commit instead of the released version of the QDF. You have to know where to look to see the that there is a difference between the two.

I don't have a perfect solution for the problem, but I have two suggestions.

1. By visiting the the GitHub-page the Qlik-Deployment-Framework/README.md I would be helped with an indication to the version number that this is not the released version eg
   QDF version 1.7.2 (adjusted).

2. More frequent releases, adding a SR to minor bug fixes like 1.7.2 SR1 and 1.7.2 SR2 or just increase the version number per committed bug fix. 1.7.3 and 1.7.4.

Cheers
Vegar

The field WeekYear is irrgeular formatted => The first 9 weeks are single digit and all others are double digit.
This behaviour can't be observed for MonthYear, where all months are double digit.

This also leads me to believe that the field WeekYear is not properly recognized by Qlik when using Date#(weekYear, 'WW-YYYY').

And leads to the wrong sorting when using WeekYear as Dimension.
Qlik will sort like the following:

38-2020 | 39-2020 | 4-2020 | 40-2020 | 41-2020

4-2020 shouldn't be in there.

Fix:
On Line 105 Change the extraction of week to => Num(Week([$vL.QDF.DateField…]),’00’)…
This will format the week to double digit and sort it correctly.

Thank you for providing this Framework!

Hi,

I have downloaded QDF 1.7.5 and installed on MS Server 2019 OS running on VM
No errors on QDF install
After QDF install, in QDF Settings i only folder option to create Dev / Test / Prod.
I don't see the option to create Qlik Sense container only.
Default is QlikView

.

It is not possible in a simple manner to get the ETLLogEntry to log its default parameter values when in need of changing one of the later parameters.

Scenario
I want to change the vL.LogName when using ETLLogEntry, but to keep all the other parameters default values. This is not possible by simple means as it not possible to explicit send Null values into a parameter of an sub.

Suggestion
I suggest that the ETLLogEntry should treat en empty string similar as null(). By doing so the following call would return all default values exept for the vL.LogName.

CALL ETLLogEntry('A','','','','Your Log')

I'm using QDF 1.7.1
whenever I call the LCGV('my_container','QVD');
I get a warning saying that vG.QVDGENBasePath missing
the same happens if I try to link to Example, Admin, or Shared containers

Hi,

After upgrading from 1.7.4 to 1.7.5, when using the "deploy tool" to create a new container, I'm receiving this error:

"root path" does not exist. Could not find file 'RootPath\ContainerName\InitLinkSkip.qvs'.

I have downloaded and placed this new version source files, including the InitLinkSkip.qvs, into the Qlik-Deployment-Framework-master folder (where 3.include and release folder are).
Also, on the Administration container, the example container and the main root. Still getting this error
Any clue what the problem could be ?

Best regards,
Cristian

The ETLLogEntry's last parameter vL.LogName - the name of the output log table doesn't have any use once the first ETLLogEntry is done. This because the output field names are the same in every call and Qlik will do an autoconcatenate and hence ignore the value in the parameter.

Consider these two calls:

CALL ETLLogEntry('TableA', '', '', '', 'My log');
CALL ETLLogEntry('TableB', '', '', '', 'Your log');

They will return a single log table consisting of two rows and not as expected two log tables with one row each.

My suggestion is that we remove the final parameter from the sub to avoid confusion. If the output table name could instead be controlled by an input variable simular to how its often done in the QVC library. Alternatively we could adjust the sub to return unique log tables based on the vL.LogName parameter. It is possible by simple means by adding some qualifying feature of the field names, but I'm in favour of my first suggestion as I don't see the need of multiple log tables.

The WeekYear string representation is defined like this
Week(...) & '-' & year(...)

In certain scenarios the year part can become wrong. Consider January 2nd 2021. It is week 53 and year 2021, but storing it as 53-2021 would be wrong as the week should be named 53-2020.

I suggest replacing the Year() function in the script with the more suited function WeekYear() that should return 2021 and not 2020 for January 2nd 2021.

When a container is created with the 'QlikDeploymentFramework.exe', the function QVDReduce is never loaded. After looking at deployed code, the line that loads the file '14.QVDReduce.qvs' is not present in 99.LoadAll.qvs.

One of the output fields in the csv table generated by the SUB WriteETLLog is named Environment.
This field is not documented nor supported by the sub creating the entries ETLLogEntry.

Looking into the script I notice an reference to variable vL.QDF like this: $(vL.QDF)' as Environment. vL.QDF is also not documumented in the sub script documentation nor the Functional reference guide.

See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.TypeInitializationException: The type initializer for 'QVDeploymentFramework.Form1' threw an exception. ---> System.Configuration.ConfigurationErrorsException: Configuration system failed to initialize ---> System.Configuration.ConfigurationErrorsException: Unrecognized configuration section System.Windows.Forms.ApplicationConfigurationSection. (D:\Qlik\00.Admin\0.Software\QlikDeploymentFramework_Deploy_Tool\QlikDeploymentFramework.exe.Config line 3)
at System.Configuration.ConfigurationSchemaErrors.ThrowIfErrors(Boolean ignoreLocal)
at System.Configuration.BaseConfigurationRecord.ThrowIfParseErrors(ConfigurationSchemaErrors schemaErrors)
at System.Configuration.BaseConfigurationRecord.ThrowIfInitErrors()
at System.Configuration.ClientConfigurationSystem.EnsureInit(String configKey)
--- End of inner exception stack trace ---
at System.Configuration.ConfigurationManager.PrepareConfigSystem()
at System.Configuration.ConfigurationManager.get_AppSettings()
at QVDeploymentFramework.Form1..cctor()
--- End of inner exception stack trace ---
at QVDeploymentFramework.Form1.extractZIP(Byte[] ZipResource, String ZipName)
at QVDeploymentFramework.Form1.Form1_Load(Object sender, EventArgs e)
at System.Windows.Forms.Form.OnLoad(EventArgs e)
at System.Windows.Forms.Form.OnCreateControl()
at System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible)
at System.Windows.Forms.Control.CreateControl()
at System.Windows.Forms.Control.WmShowWindow(Message& m)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ScrollableControl.WndProc(Message& m)
at System.Windows.Forms.Form.WmShowWindow(Message& m)
at System.Windows.Forms.Form.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

************** Loaded Assemblies **************
mscorlib
Assembly Version: 4.0.0.0
Win32 Version: 4.7.2114.0 built by: NET47REL1LAST
CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll

QlikDeploymentFramework
Assembly Version: 1.7.1.0
Win32 Version: 1.7.1.0
CodeBase: file:///D:/Qlik/00.Admin/0.Software/QlikDeploymentFramework_Deploy_Tool/QlikDeploymentFramework.exe

System.Windows.Forms
Assembly Version: 4.0.0.0
Win32 Version: 4.7.2114.0 built by: NET47REL1LAST
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll

System
Assembly Version: 4.0.0.0
Win32 Version: 4.7.2114.0 built by: NET47REL1LAST
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll

System.Drawing
Assembly Version: 4.0.0.0
Win32 Version: 4.6.1099.0 built by: NETFXREL4STAGE
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll

System.Configuration
Assembly Version: 4.0.0.0
Win32 Version: 4.6.1087.0 built by: NETFXREL4STAGE
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll

System.Core