QFQ Merge » History » Version 15
Enis Nuredini, 24.06.2024 15:27
1 | 1 | Enis Nuredini | h1. QFQ Merge |
---|---|---|---|
2 | |||
3 | {{toc}} |
||
4 | |||
5 | h2. Installation |
||
6 | |||
7 | QFQ Merge feature should be installed automatically with new QFQ Version 24.3.x |
||
8 | If the automatic upgrade wasnt successful, here are some important points: |
||
9 | |||
10 | h3. SQL Function and Procedure |
||
11 | |||
12 | QFQ should deliver one sql function and one procedure called: |
||
13 | * build_dynamic_columns |
||
14 | * auto_insert_merge_rules |
||
15 | |||
16 | 2 | Enis Nuredini | If one of these is missing then take these SQL statement to import it: |
17 | 1 | Enis Nuredini | attachment:build_dynamic_columns.sql |
18 | attachment:auto_insert_merge_rules.sql |
||
19 | 3 | Enis Nuredini | |
20 | h3. Grp Table |
||
21 | |||
22 | Check if the table 'Grp' exists in database. |
||
23 | Table should have following columns: |
||
24 | * id |
||
25 | * grId |
||
26 | * name |
||
27 | * reference |
||
28 | * value |
||
29 | * value2 |
||
30 | * value3 |
||
31 | * value4 |
||
32 | * comment |
||
33 | * enabled |
||
34 | * modified |
||
35 | * created |
||
36 | |||
37 | 4 | Enis Nuredini | SQL structure: attachment:Grp.sql |
38 | |||
39 | 3 | Enis Nuredini | In this table two records with following references should already exist: |
40 | * qfq_merge_rule |
||
41 | * qfq_merge_query |
||
42 | 5 | Enis Nuredini | |
43 | SQL Merge Records: attachment:Grp_merge_data.sql |
||
44 | 6 | Enis Nuredini | |
45 | h3. QFQ Merge Page |
||
46 | |||
47 | Create for the merge tool a new page in Typo3 backend if not already done. |
||
48 | 7 | Enis Nuredini | Create a new qfq tt-content on that page with following content (http://docs.qfq.io/en/master/Report.html#merge-tool): |
49 | 6 | Enis Nuredini | <pre> |
50 | file=_mergeData |
||
51 | </pre> |
||
52 | 8 | Enis Nuredini | |
53 | h2. Configuration |
||
54 | |||
55 | h3. New Rules |
||
56 | |||
57 | Let's trigger the automation to create some new rules depending on a beginning pId column name: |
||
58 | 11 | Enis Nuredini | !{width:300px}qfq_merge_rule_01.png! !{width:300px}qfq_merge_rule_02.png! |
59 | 12 | Enis Nuredini | |
60 | After a page reload all created rules should be displayed in the table. |
||
61 | The auto created rules are all per default enabled. It's possible to edit, delete or create new rules. |
||
62 | An example of a special rule: |
||
63 | !qfq_merge_rule_03.png! |
||
64 | |||
65 | h3. New Search Query |
||
66 | |||
67 | Create a new search query. |
||
68 | Its important to use the predefined keywords: |
||
69 | * _tableName |
||
70 | * _id1 |
||
71 | * _id2 |
||
72 | * _column1 |
||
73 | * _column2 |
||
74 | * _key |
||
75 | |||
76 | !qfq_merge_query_01.png! |
||
77 | |||
78 | Example of a query can be found here: http://docs.qfq.io/en/master/Report.html#merge-tool |
||
79 | 13 | Enis Nuredini | |
80 | h2. Usage |
||
81 | |||
82 | Select the data on which you want to proceed the merge: |
||
83 | !qfq_merge_01.png! |
||
84 | |||
85 | As default the primary record with lower ID is selected to keep: |
||
86 | !qfq_merge_02.png! |
||
87 | |||
88 | It's important to know that the merge tool focuses on the linked records. The comparsion and merge of the data from the primary table itself should be done by the user manually. It's helpful to define the output of these data in the search query (_column1, _column2). |
||
89 | !qfq_merge_03.png! |
||
90 | |||
91 | 14 | Enis Nuredini | Select the records you want to merge with the selected primary ID (keep). Unselected records will be deleted and records with a dash will not be changed. |
92 | 15 | Enis Nuredini | !qfq_merge_04.png! |