Giter VIP home page Giter VIP logo

inqlik-tools's People

Contributors

vadimtsushko avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

inqlik-tools's Issues

Custom file name in relative build paths (Feature request)

Feature request

I've started a new project where we are multiple developers using sublime for development pushing and pulling QDF container releases from GIT.

Our qvw (qvf) files are build up of multiple qvs-files that we include in the script. On top of each qvs file we add the absolute build path.

//#!c:\Dev\Veglar\1.MyContainer\1.Application\TheApplication.qvw   

The full path causes trouble when committing , hence each developer have its own development path each developer needs to change the path every time another developer have committed code to the master repoitory,

//#!..\..\1.Application\

To use relative path the qlikview-application need to be named as the same as the qvs which will not be the case when we are including multiple qvs-files into the same application.

I would love to see an extensioin to the relative buld path to even accept custom qvw-file names.

//#!..\..\1.Application\TheApplication.qvw   

PS: Did you see that Qlik mentioned InQlik tools in their Qlik IDE Development environment document

Not recognising qdf variables

The documentation aroud using the QlikView script syntax checker from inqlik CLI needs an overview.
I tried running the syntax checker while using QDF and run into trouble. See error below.

------------------------------
 $(must_Include=$(vG.LocalePath)2.Swe.qvs);
>>>>> Parse error. File: "C:\QDF\1.Production\100.System\2.Extract.Excel\3.Include\99.Extract.Excel\Main.qvs", line: 4 col: 1 message: Variable vG.LocalePath not defined
------------------------------

I notice the following in the settings file, but no documentation on how to use it.

// Implicit include file (use it for example to declare predefined variables of QlikView Deployment Framework) 
  "qv_script_check_syntax_impicit_include_file": "default_inqlude.qvs"

(I have managed to run scripts with qdf variables before without any modification, but I don't know why it does not work all the time)

Expand variables and export file

Hi, I want to use the function "Expand variables and export file", but based on the description it´s not doing anything with my script. How could this function be used? Could you give an example please? Regards, Thomas

Another bug in export in qvs format

Formulas like Money($(Sales)/$(SalesBudget)),'# ##0,0%') end up with chr(39) in QlikView app.
Like Money($(Sales)/$(SalesBudget)),chr(39)# ##0,0%chr(39))

QVD viewer needs to quote fields with strings

When the qvd viewer creates a sample load statement it would be helpful if it quoted fields needing it.
I the example below Qty_ per Unit of Measure needs to be "Qty_ per Unit of Measure" or possible as I prefer it [Qty_ per Unit of Measure]

LOAD
  Item No_,
  Code,
  Qty_ per Unit of Measure,
  Length,
  Width,
  Height,
  Cubage,
  Weight
    FROM [C:\path\to\some\file.qvd] (QVD);

Opening Qlikview file fails

Ctrl-Shift-B key combination opens corresponding qlikview application instead of reloading it

I have trouble making InQlik Tools to open my application. My guess is that there is an issue with the string command for opening qv.exe.

I get this error both when I use the default path for builds and when I point it out using
//#!C:\My path\My report.qvw OR
//#!..\My relative path\My report.qvw

Note: Running the script (Ctrl-B) works fine without any issues.

I attached the log that is presented in Sublime Text when pressing Ctrl-Shift-B

'c:\Program' is not recognized as an internal or external command, operable program or batch file. [Finished in 0.0s with exit code 1] [cmd: ['cmd', '/C', 'c:\\Program Files\\QlikView\\qv.exe', 'C:\\Users\\vegarn\\Documents\\My report\\3_Load\\fdw\\Report.qvw']] [dir: C:\Users\vegarn\Documents\My report\3_Load\fdw] [path: C:\ProgramData\Oracle\Java\javapath;D:\app\vegarn\product\12.1.0\client_2;D:\app\vegarn\product\12.1.0\client_1;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files\TortoiseSVN\bin;C:\Program Files (x86)\Hewlett-Packard\HP Performance Advisor]

Commenting lines

Приветствую,
Почему может не работать в сублимтексте комментирование строк комбинацией CTRL+ / ?

Change ´Ctrl-Shift-L´ key combination

This key combination is used for the option ´Selection->Split into lines´, it allows the creation of multiple cursors from selected text, one cursor per line.

Dollar expansions in QVS variable file

There is an bug in the dollar expansion handling in the InQlik Variable tool.
When exporting to qvs you change all $ with @ before writing it in the script, then you replace it with chr(39) not chr(36) as you should.


---
set:vL.sum
definition:sum([$(=DynExp)])

---

The current output looks like:

let vL.sum = replace(replace('sum([@(=DynExp)])','~~~', 'chr(39)'), '@(', chr(39) & '(');

but it should be:
let vL.sum = replace(replace('sum([@(=DynExp)])','~~~', 'chr(39)'), '@(', chr(36) & '(');

Cheers
Vegar

README markdown issues

put spaces after the tags like ## or ### or ##### ....

your markdown isn't working because you have no spaces after the hashes (it makes it really hard to read your docs).

Multi line variable does not format properly within QlikView

Hello Vadim,

I hope this message finds you well.

I've notice there is no way to keep format of the multi line variables. All variables appear in QlikView in one line. Would you advice if that's by design or there is a way to fix it. I've tried with YAML multi line convention by adding | at the beginning of the string:
capture

Many thanks in advance for your help.

Best regards,
Janusz

Syntax coloring break when using qdf naming convension on variables

The color markup of an variable name is not correct when using qdf standard naming convension such as vL.variablename or vG.variablename. I'm guessing it is the dot (.) that breaks the highlighting.


---
set: vG.SalesSum
definition: Sum({<OperationType={Sale}>} Amount)

---

//Vegar Lie Arntsen

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.