Is it possible to implement a tool on the server that enables clients to customize their most frequent multiple fields selections?
Ex. clients in Russia will most of the time select
Product X, Russia
but not client in Brazil...
The tool could for instance capture the current selection. There could be a pop-up window for choosing the selection's name, plus other features, like delete a selection...
Is it feasible ? Can i prototype an equivalent tool on the client Personal Edition?
What if i want the user to be able to propose its own logic, as for instance: select, or export to Excel, all entries which verified some inequalities?
Enabling the user to implement his own logic on the server might be possible e.g. by enabling the shared server objects feature, thus enabling the user to create his own chart objects. This works to some extend, but also has some drawbacks, because the shared server objects are stored in a separate meta file on the server next to the qvw document and this might impact maintenance, especially if you want to distribute the logic then to more / all users.
Another option is to let your power users design / modify QV front end applications (.qvw) files.
Both options require that the user knows the data model to some extend and is also has some QV front end experience / knowledge, also with regard to QV functions / expressions.
Both options will be limited when it comes to logic that benifits from changes to the data model.
You don't want everybody to change your model, so this would require that the logic will be defined in requirements and put into code by your developers.
Export to Excel is a standard feature available in most charts, so this should be no problem as soon as the chart is designed properly.
Selecting all entries with some inequalities might be easy, if the inequalities can be selected easily just by using the list boxes (e.g. by using the search), or can be difficult to achieve with only front end tools, without preparing something in your data model. So this question is not easy to answer.
Both are possible, shared objects or direct implementation into QLikView
Would you have a reference explaining the shared server objects?
Most surely, i will go for 2/. I will prepare detailled requirements for direct development on the server
There would be two types of tools
some proposed tools for recurrent actions, for instance a drop down list on right click or in the menu with possible actions, s.a. select fields verifying some criteria...
some tools/wizard for customization of criteria. is this an option, and where can i look to have more info?
Just some ideas with standard functionality (there are also third party tools and extensions you can look into):
- For recurrrent actions, create buttons with button actions (like performing selections in field with some criteria, also dynamic criteria based on current selection / input variables)
- Customization of criteria:
Use variables (edited in input boxes or using variable expressions that define the variable based on current selections etc.)
Use user bookmarks to extend the predefined document bookmarks
