Skip to main content
Woohoo! Qlik Community has won “Best in Class Community” in the 2024 Khoros Kudos awards!
Announcements
Nov. 20th, Qlik Insider - Lakehouses: Driving the Future of Data & AI - PICK A SESSION
cancel
Showing results for 
Search instead for 
Did you mean: 
Not applicable

IndexMonitor 0.1: Creation Date shows number not date

Hallo,

IndexMonitor on a operation system in german mode displays numbers with a comma as decimal point. How to fix this?

Ragards

Frank

1 Solution

Accepted Solutions
qliknerd
Contributor III
Contributor III

Hi Frank, in the IndexMonitor make sure you update the LocalePath in that script too:

$(Include=$(vG.LocalePath)\10.Ger.qvs);

View solution in original post

6 Replies
Magnus_Berg
Employee
Employee

Hi Frank, could you provide some more information? The app or images...

Thx /Magnus

Not applicable
Author

Hallo Magnus,

thx you for your time

My App just works as follows (short version):

1) Init QVS this way:

#####################################

// Advanced search for 1.Init.qvs only works with 0.95 or later

// Script to automatically identify and start Deployment Framework

// Based on InitLink.qvs stored in vG.BasePath

// Identifying Container based on InitLink.qvs

let vG.BasePath=;

SET vL.Path_tmp = ;

for vL.x =1 to 10-1

    LET vL.Path='..\'&'$(vL.Path_tmp)';

    LET vL.Path_tmp='$(vL.Path)';

    $(Include=$(vL.Path)InitLink.qvs);

    exit for when not '$(vG.BasePath)'= ''

    next

SET vL.Path = ;

SET vL.Path_tmp = ;

SET vL.x = ;

$(Include=$(vG.SubPath)\4.GenericContainerLoader.qvs);

exit script when '$(vG.BasePath)'= '' ;

######################################

2) Switch to German mode and load all subs

$(Include=$(vG.SharedLocalePath)\10.Ger.qvs)

$(Include=$(vG.SubPath)\99.LoadAll.qvs)

3) After the load via SQL and LOAD statement doing Store and IndexAdd

Store [$(vL.TableName)] into '$(vG.QVDPath)\$(vL.TableName).qvd';

Call IndexAdd('$(vG.QVDPath)\$(vL.TableName).qvd');

4) The index file created in ..\QDF\99.Shared_Folders\5.Config\Index\<ContainerName>\2.QVD\<TablenName>.qvd.Index

hast got the value 42233,419293981 for QVDTimestamp.

5) IndexMonitor at ..\QDF\0.Administration\1.Application\3.IndexMonitor\IndexMonitor.qvw shows the same string as you could see in the attachment

qliknerd
Contributor III
Contributor III

Hi Frank, in the IndexMonitor make sure you update the LocalePath in that script too:

$(Include=$(vG.LocalePath)\10.Ger.qvs);

Not applicable
Author

Hallo qliknerd,

thanks for that. I tried this approach before but did a mistake. I had changed it to $(Include=$(vG.LocalePath)\1.Ger.qvs); but that did not work (as you would expect).

So changing to Must_include

$(Must_Include=$(vG.LocalePath)\1.Ger.qvs);

would have given an error.

So my wish to future versions of IndexMonitor is a more generic approach so that changing that line after each QDF update is not necessary for users with a no United States locale. And use of Must_include

Also, the format in the column is not a german format. German format is DD.MM.YYYY ....

Magnus_Berg
Employee
Employee

Hi Frank, have you tried to change format pattern in the table property box to System?TimeFormat.PNG
Best regards

Magnus

Not applicable
Author

Hallo Magnus,

thx, but this was an misunderstanding. I know that one can change the format pattern. It was just a feedback for the developers of IndexMonitor and a wish to fix this in future versions.

So in future posts I will try to express more clearly what I mean and what my thoughts are.

But still thx for your answer.

Regards

Frank