{"id":55144,"date":"2020-01-13T00:00:00","date_gmt":"2020-01-12T21:00:00","guid":{"rendered":"https:\/\/prohoster.info\/blog\/blog_prohoster\/tableau-v-roznitse-realno"},"modified":"2020-02-18T14:03:13","modified_gmt":"2020-02-18T11:03:13","slug":"tableau-v-roznitse-realno","status":"publish","type":"post","link":"https:\/\/prohoster.info\/sq\/blog\/news\/tableau-v-roznitse-realno","title":{"rendered":"Tableau n\u00eb pakic\u00eb, realisht?","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"<p><b>Koha e raportimit n\u00eb Excel po ik\u00ebn me shpejt\u00ebsi \u2014 prirja drejt mjeteve m\u00eb t\u00eb p\u00ebrshtatshme p\u00ebr paraqitjen dhe analiz\u00ebn e informacionit \u00ebsht\u00eb e dukshme n\u00eb t\u00eb gjitha fushat. Prej koh\u00ebsh kishim diskutuar brenda kompanis\u00eb dixhitalizimin e nd\u00ebrtimit t\u00eb raportimit dhe zgjodh\u00ebm sistemin e vizualizimit dhe analitik\u00ebs self-service Tableau. Aleksandr Bezuglyi, drejtues i departamentit t\u00eb zgjidhjeve analitike dhe raportimit t\u00eb Grupit \u00abM.Video-Eldorado\u00bb, tregoi p\u00ebr p\u00ebrvoj\u00ebn dhe rezultatet e krijimit t\u00eb nj\u00eb dashboard-i operacional.<\/b><\/p>\n<p>Po e them menj\u00ebher\u00eb: jo gjith\u00e7ka q\u00eb kishim planifikuar arrit\u00ebm ta realizonim, por p\u00ebrvoja ishte interesante dhe shpresoj q\u00eb t\u00eb jet\u00eb e dobishme edhe p\u00ebr ju. N\u00ebse dikush ka ide se si mund t\u00eb ishte b\u00ebr\u00eb m\u00eb mir\u00eb, do t\u2019i jem shum\u00eb mir\u00ebnjoh\u00ebs p\u00ebr k\u00ebshillat dhe sugjerimet.<\/p>\n<p><img decoding=\"async\" alt=\"Tableau n\u00eb pakic\u00eb, realisht?\" src=\"\/wp-content\/uploads\/2020\/01\/81c41899e9b3acf1858a4faa627c121b.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nM\u00eb posht\u00eb flasim p\u00ebr at\u00eb me \u00e7far\u00eb u p\u00ebrball\u00ebm dhe \u00e7far\u00eb m\u00ebsuam.<br \/>\n<noindex><a rel=\"nofollow\" name=\"habracut\"><\/a><\/noindex><\/p>\n<h4>Si e nis\u00ebm<\/h4>\n<p>\nTe \u00abM.Video-Eldorado\u00bb ekziston nj\u00eb model i mir\u00ebpunuar i t\u00eb dh\u00ebnave: informacion i strukturuar me thell\u00ebsin\u00eb e nevojshme t\u00eb ruajtjes dhe nj\u00eb num\u00ebr shum\u00eb i madh raportesh me form\u00eb fikse (shihni m\u00eb shum\u00eb holl\u00ebsi <noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/mvideo\/blog\/462015\/\">k\u00ebt\u00eb artikull<\/a><\/noindex>). Mbi baz\u00ebn e tyre, analist\u00ebt krijojn\u00eb ose tabela p\u00ebrmbledh\u00ebse dhe d\u00ebrgesa t\u00eb formatuara n\u00eb Excel, ose prezantime t\u00eb bukura n\u00eb PowerPoint p\u00ebr p\u00ebrdoruesit fundor\u00eb.<\/p>\n<p>Rreth dy vjet m\u00eb par\u00eb, n\u00eb vend t\u00eb raporteve me form\u00eb fikse, nis\u00ebm t\u00eb krijonim raporte analitike n\u00eb SAP Analysis (nj\u00eb shtes\u00eb p\u00ebr Excel, n\u00eb thelb \u2014 nj\u00eb tabel\u00eb p\u00ebrmbledh\u00ebse mbi nj\u00eb motor OLAP). Por ky mjet nuk arriti t\u00eb mbulonte nevojat e t\u00eb gjith\u00eb p\u00ebrdoruesve, ndaj shumica vazhduan t\u00eb p\u00ebrdornin informacionin e p\u00ebrpunuar m\u00eb tej nga analist\u00ebt.<\/p>\n<p>P\u00ebrdoruesit tan\u00eb fundor\u00eb ndahen n\u00eb tri kategori:<\/p>\n<p><b>Menaxhmenti i lart\u00eb<\/b>. K\u00ebrkon informacion n\u00eb nj\u00eb form\u00eb t\u00eb prezantuar mir\u00eb dhe leht\u00ebsisht t\u00eb kuptueshme vizualisht.<\/p>\n<p><b>Menaxhmenti i mes\u00ebm<\/b>, p\u00ebrdorues t\u00eb avancuar. Jan\u00eb t\u00eb interesuar p\u00ebr eksplorimin e t\u00eb dh\u00ebnave dhe jan\u00eb n\u00eb gjendje t\u00eb nd\u00ebrtojn\u00eb vet\u00eb raporte n\u00ebse kan\u00eb mjetet e duhura. Pik\u00ebrisht ata u b\u00ebn\u00eb p\u00ebrdoruesit kryesor\u00eb t\u00eb raporteve analitike n\u00eb SAP Analysis.<\/p>\n<p><b>P\u00ebrdoruesit masiv\u00eb<\/b>. Nuk jan\u00eb t\u00eb interesuar p\u00ebr analiz\u00eb t\u00eb pavarur t\u00eb t\u00eb dh\u00ebnave; p\u00ebrdorin raporte me shkall\u00eb t\u00eb kufizuar lirie, n\u00eb formatin e d\u00ebrgesave dhe tabelave p\u00ebrmbledh\u00ebse n\u00eb Excel.<\/p>\n<p>Ideja jon\u00eb ishte t\u00eb mbulonim nevojat e t\u00eb gjith\u00eb p\u00ebrdoruesve dhe t\u2019u ofronim nj\u00eb mjet unik e t\u00eb p\u00ebrshtatsh\u00ebm. Vendos\u00ebm t\u00eb nisnim nga top-menaxhmenti. Atyre u nevojiteshin panele t\u00eb p\u00ebrshtatshme p\u00ebr analiz\u00ebn e rezultateve kryesore t\u00eb biznesit. K\u00ebshtu, e nis\u00ebm me Tableau dhe fillimisht zgjodh\u00ebm dy drejtime: treguesit e shitjeve n\u00eb retail dhe online, me thell\u00ebsi dhe gjer\u00ebsi t\u00eb kufizuar analize, q\u00eb do t\u00eb mbulonin rreth 80% t\u00eb t\u00eb dh\u00ebnave t\u00eb k\u00ebrkuara nga top-menaxhmenti.<\/p>\n<p>Meqen\u00ebse p\u00ebrdoruesit e dashboard-eve ishin drejtuesit e lart\u00eb, u shfaq edhe nj\u00eb KPI shtes\u00eb i produktit \u2013 shpejt\u00ebsia e reagimit. Askush nuk do t\u00eb pres\u00eb 20-30 sekonda derisa t\u00eb p\u00ebrdit\u00ebsohen t\u00eb dh\u00ebnat. Navigimi duhej t\u00eb p\u00ebrfundonte brenda 4-5 sekondash, ose edhe m\u00eb mir\u00eb, t\u00eb funksiononte menj\u00ebher\u00eb. Fatkeq\u00ebsisht, k\u00ebt\u00eb nuk arrit\u00ebm ta realizonim.<\/p>\n<p>K\u00ebshtu dukej prototipi i dashboard-it ton\u00eb kryesor:<\/p>\n<p><img decoding=\"async\" alt=\"Tableau n\u00eb pakic\u00eb, realisht?\" src=\"\/wp-content\/uploads\/2020\/01\/a7a028feee6542dfbc1fd3c2feeaa3de.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nIdeja kryesore ishte t\u00eb bashkonim n\u00eb t\u00eb majt\u00eb drejtuesit kryesor\u00eb t\u00eb KPI-ve, t\u00eb cil\u00ebt n\u00eb fund arrit\u00ebn n\u00eb 19, dhe n\u00eb t\u00eb djatht\u00eb t\u00eb paraqisnim dinamik\u00ebn e tyre dhe ndarjen sipas atributeve kryesore. Detyra duket e thjesht\u00eb, nd\u00ebrsa vizualizimi logjik dhe i kuptuesh\u00ebm, derisa t\u00eb futesh n\u00eb detaje.<\/p>\n<h2>Detaji 1. V\u00ebllimi i t\u00eb dh\u00ebnave<\/h2>\n<p>\nTabela kryesore e shitjeve p\u00ebr nj\u00eb vit z\u00eb tek ne rreth 300 milion\u00eb rreshta. Meqen\u00ebse duhet t\u00eb pasqyrohet edhe dinamika krahasuar me vitin e kaluar dhe me paraardh\u00ebsin e tij, v\u00ebllimi i t\u00eb dh\u00ebnave vet\u00ebm p\u00ebr shitjet faktike arrin rreth 1 miliard rreshta. P\u00ebrve\u00e7 k\u00ebsaj, ve\u00e7mas ruhet informacioni p\u00ebr t\u00eb dh\u00ebnat e planifikuara dhe blloku i shitjeve online. Prandaj, edhe pse p\u00ebrdor\u00ebm DB in-memory me kolona SAP HANA, shpejt\u00ebsia e ekzekutimit t\u00eb nj\u00eb k\u00ebrkese me p\u00ebrzgjedhjen e t\u00eb gjith\u00eb treguesve p\u00ebr nj\u00eb jav\u00eb nga depozitat aktuale n\u00eb koh\u00eb reale ishte rreth 15-20 sekonda. Zgjidhja e k\u00ebtij problemi duket e qart\u00eb vetvetiu \u2013 materializim shtes\u00eb i t\u00eb dh\u00ebnave. Por edhe k\u00ebtu ka sfida t\u00eb fshehura, p\u00ebr t\u00eb cilat m\u00eb posht\u00eb.<\/p>\n<h2>Detaji 2. Tregues joaditiv\u00eb<\/h2>\n<p>\nTek ne shum\u00eb KPI varen nga numri i kupon\u00ebve fiskal\u00eb. Dhe ky tregues p\u00ebrfaq\u00ebson COUNT DISTINCT t\u00eb numrit t\u00eb rreshtave (header-at e kupon\u00ebve) dhe jep shuma t\u00eb ndryshme n\u00eb var\u00ebsi t\u00eb atributeve t\u00eb zgjedhura. P\u00ebr shembull, ja si duhet t\u00eb llogaritet ky tregues dhe ai derivat prej tij:<\/p>\n<p><img decoding=\"async\" alt=\"Tableau n\u00eb pakic\u00eb, realisht?\" src=\"\/wp-content\/uploads\/2020\/01\/0a6d676f0a5c2b779a5e7892b1f54929.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nP\u00ebr korrekt\u00ebsin\u00eb e llogaritjeve mund t\u00eb b\u00ebhet:<\/p>\n<ul>\n<li>T\u00eb kryhet llogaritja e treguesve t\u00eb till\u00eb n\u00eb koh\u00eb reale n\u00eb depozit\u00eb;\n<\/li>\n<li>T\u00eb kryhet llogaritja mbi t\u00eb gjith\u00eb v\u00ebllimin e t\u00eb dh\u00ebnave n\u00eb Tableau, pra sipas k\u00ebrkes\u00ebs t\u2019i d\u00ebrgohen Tableau t\u00eb gjitha t\u00eb dh\u00ebnat sipas filtrave t\u00eb zgjedhur n\u00eb granularitetin e pozicioneve t\u00eb kupon\u00ebve fiskal\u00eb;\n<\/li>\n<li>T\u00eb krijohet nj\u00eb pamje e materializuar, ku do t\u00eb llogariten t\u00eb gjith\u00eb treguesit p\u00ebr t\u00eb gjitha variantet e p\u00ebrzgjedhjeve q\u00eb japin rezultate t\u00eb ndryshme joadditive.\n<\/li>\n<\/ul>\n<p>\n\u00cbsht\u00eb e qart\u00eb se n\u00eb shembullin UTE1 dhe UTE2 jan\u00eb atribute t\u00eb materialit q\u00eb p\u00ebrfaq\u00ebsojn\u00eb hierarkin\u00eb e produkteve. Kjo nuk \u00ebsht\u00eb di\u00e7ka statike; p\u00ebrmes saj kryhet menaxhimi i brendsh\u00ebm i kompanis\u00eb, pasi p\u00ebr grupe t\u00eb ndryshme produktesh p\u00ebrgjigjen menaxher\u00eb t\u00eb ndrysh\u00ebm. Kemi pasur shum\u00eb rishikime globale t\u00eb k\u00ebsaj hierarkie, kur ndryshonin t\u00eb gjitha nivelet dhe rishikoheshin nd\u00ebrlidhjet, si edhe ndryshime t\u00eb vazhdueshme t\u00eb synuara, kur nj\u00eb grup kalon nga nj\u00eb nyje n\u00eb tjetr\u00ebn. N\u00eb raportimin e zakonsh\u00ebm, e gjith\u00eb kjo llogaritet n\u00eb koh\u00eb reale nga atributet e materialit; n\u00eb rastin e materializimit t\u00eb k\u00ebtyre t\u00eb dh\u00ebnave, duhet t\u00eb zhvillohet nj\u00eb mekaniz\u00ebm p\u00ebr ndjekjen e k\u00ebtyre ndryshimeve dhe ringarkimin automatik t\u00eb t\u00eb dh\u00ebnave historike. Nj\u00eb detyr\u00eb mjaft jotriviale.<\/p>\n<h2>Detaji 3. Krahasimi i t\u00eb dh\u00ebnave <\/h2>\n<p>\nKy element \u00ebsht\u00eb i ngjash\u00ebm me t\u00eb m\u00ebparshmin. Thelbi \u00ebsht\u00eb se n\u00eb kompani, gjat\u00eb analiz\u00ebs, \u00ebsht\u00eb praktik\u00eb t\u00eb formohen disa nivele krahasimi me periudh\u00ebn e m\u00ebparshme:<\/p>\n<p><i>Krahasimi me periudh\u00ebn e m\u00ebparshme (dit\u00eb me dit\u00eb, jav\u00eb me jav\u00eb, muaj me muaj)<\/i><\/p>\n<p>N\u00eb k\u00ebt\u00eb krahasim supozohet q\u00eb, n\u00eb var\u00ebsi t\u00eb periudh\u00ebs s\u00eb zgjedhur nga p\u00ebrdoruesi (p\u00ebr shembull java e 33-t\u00eb e vitit), ne duhet t\u00eb tregojm\u00eb dinamik\u00ebn ndaj jav\u00ebs s\u00eb 32-t\u00eb; n\u00ebse do t\u00eb zgjidhnim t\u00eb dh\u00ebnat p\u00ebr nj\u00eb muaj, p\u00ebr shembull majin, at\u00ebher\u00eb ky krahasim do t\u00eb tregonte dinamik\u00ebn ndaj prillit.<\/p>\n<p><i>Krahasimi me vitin e kaluar<\/i><\/p>\n<p>K\u00ebtu nuanca kryesore \u00ebsht\u00eb se, kur krahasoni sipas dit\u00ebve dhe jav\u00ebve, nuk merrni t\u00eb nj\u00ebjt\u00ebn dit\u00eb t\u00eb vitit t\u00eb kaluar, pra nuk mund t\u00eb vendosni thjesht viti aktual minus nj\u00eb. Duhet t\u00eb shikoni dit\u00ebn p\u00ebrkat\u00ebse t\u00eb jav\u00ebs. Nd\u00ebrsa kur krahasoni muajt, p\u00ebrkundrazi, duhet t\u00eb merrni sakt\u00ebsisht t\u00eb nj\u00ebjt\u00ebn dit\u00eb kalendarike t\u00eb vitit t\u00eb kaluar. Ka gjithashtu nuanca q\u00eb lidhen me vitet e brishta. N\u00eb depozitat burimore, i gjith\u00eb informacioni \u00ebsht\u00eb i shp\u00ebrndar\u00eb sipas dit\u00ebve; atje nuk ka fusha t\u00eb ve\u00e7anta p\u00ebr jav\u00eb, muaj apo vite. Prandaj, p\u00ebr t\u00eb marr\u00eb nj\u00eb pamje t\u00eb plot\u00eb analitike n\u00eb panel, duhet t\u00eb llogarisni jo nj\u00eb periudh\u00eb t\u00eb vetme, p\u00ebr shembull nj\u00eb jav\u00eb, por 4 jav\u00eb, dhe m\u00eb pas t\u2019i krahasoni k\u00ebto t\u00eb dh\u00ebna, t\u00eb pasqyroni dinamik\u00ebn dhe devijimet. P\u00ebrkat\u00ebsisht, kjo logjik\u00eb e formimit t\u00eb krahasimit n\u00eb dinamik\u00eb mund t\u00eb zbatohet ose n\u00eb Tableau, ose n\u00eb an\u00ebn e vitrin\u00ebs s\u00eb t\u00eb dh\u00ebnave. Po, dhe p\u00ebr k\u00ebto detaje sigurisht q\u00eb dinim dhe kishim menduar q\u00eb n\u00eb faz\u00ebn e projektimit, por ndikimi i tyre n\u00eb performanc\u00ebn e dashboard-it p\u00ebrfundimtar ishte i v\u00ebshtir\u00eb t\u00eb parashikohej.<\/p>\n<p>Gjat\u00eb zbatimit t\u00eb dashboard-it, ndoq\u00ebm nj\u00eb rrug\u00eb t\u00eb gjat\u00eb Agile. Detyra jon\u00eb ishte t\u00eb ofronim sa m\u00eb shpejt p\u00ebr testim nj\u00eb mjet funksional me t\u00eb dh\u00ebnat e nevojshme. Prandaj punuam me sprinte dhe u fokusuam n\u00eb minimizimin e pun\u00ebs n\u00eb an\u00ebn e depozit\u00ebs aktuale t\u00eb t\u00eb dh\u00ebnave.<\/p>\n<h2>Pjesa 1. Besimi te Tableau<\/h2>\n<p>\nP\u00ebr t\u00eb thjeshtuar mb\u00ebshtetjen IT dhe p\u00ebr t\u00eb p\u00ebrshpejtuar zbatimin e ndryshimeve, vendos\u00ebm q\u00eb logjika e llogaritjes s\u00eb treguesve joadditiv\u00eb dhe krahasimi i periudhave t\u00eb m\u00ebparshme t\u00eb realizoheshin n\u00eb Tableau.<\/p>\n<h3>Faza 1. Gjith\u00e7ka n\u00eb Live, pa asnj\u00eb p\u00ebrshtatje t\u00eb vitrinave.<\/h3>\n<p>\nN\u00eb k\u00ebt\u00eb faz\u00eb e lidh\u00ebm Tableau me vitrinat aktuale dhe vendos\u00ebm t\u00eb shihnim si do t\u00eb llogaritej numri i faturave p\u00ebr nj\u00eb vit.<\/p>\n<p><b>Rezultati:<\/b><\/p>\n<p>P\u00ebrgjigjja ishte d\u00ebshp\u00ebruese \u2013 20 minuta. Transferim i t\u00eb dh\u00ebnave p\u00ebrmes rrjetit, ngarkes\u00eb e lart\u00eb mbi Tableau. E kuptuam se logjika e treguesve joadditiv\u00eb duhej t\u00eb zbatohej n\u00eb HANA. Kjo nuk na trembi shum\u00eb, sepse kishim tashm\u00eb p\u00ebrvoj\u00eb t\u00eb ngjashme me BO dhe Analysis, dhe dinim t\u00eb nd\u00ebrtonim vitrina t\u00eb shpejta n\u00eb HANA q\u00eb jepnin tregues joadditiv\u00eb t\u00eb llogaritur sakt\u00eb. Tani mbetej vet\u00ebm t\u2019i p\u00ebrshtatnim ato p\u00ebr Tableau.<\/p>\n<h3>Faza 2. Optimizojm\u00eb vitrinat, pa materializim, gjith\u00e7ka n\u00eb koh\u00eb reale.<\/h3>\n<p>\nKrijuam nj\u00eb pasqyr\u00eb t\u00eb re t\u00eb ve\u00e7ant\u00eb, e cila jepte n\u00eb koh\u00eb reale t\u00eb dh\u00ebnat e nevojshme p\u00ebr TABLEAU. N\u00eb p\u00ebrgjith\u00ebsi arrit\u00ebm nj\u00eb rezultat t\u00eb mir\u00eb: e ul\u00ebm koh\u00ebn e gjenerimit t\u00eb t\u00eb gjith\u00eb treguesve nga nj\u00eb jav\u00eb n\u00eb 9-10 sekonda. Dhe, sinqerisht, prisnim q\u00eb n\u00eb Tableau koha e p\u00ebrgjigjes s\u00eb dashboard-it t\u00eb ishte 20-30 sekonda n\u00eb hapjen e par\u00eb dhe m\u00eb pas, fal\u00eb cache-it, 10-12 sekonda, gj\u00eb q\u00eb n\u00eb p\u00ebrgjith\u00ebsi do t\u00eb na k\u00ebnaqte.<\/p>\n<p><b>Rezultati:<\/b><\/p>\n<p>Hapja e par\u00eb e dashboard-it: 4-5 minuta<br \/>\n\u00c7do klikim: 3-4 minuta<br \/>\nAskush nuk e priste nj\u00eb rritje t\u00eb till\u00eb shtes\u00eb t\u00eb koh\u00ebs s\u00eb pun\u00ebs s\u00eb pasqyr\u00ebs.<\/p>\n<h2>Pjesa 2. Thellim n\u00eb Tableau<\/h2>\n<p><\/p>\n<h3>Faza 1. Analiza e performanc\u00ebs s\u00eb Tableau dhe optimizim i shpejt\u00eb<\/h3>\n<p>\nNis\u00ebm t\u00eb analizojm\u00eb se ku e shpenzon Tableau pjes\u00ebn m\u00eb t\u00eb madhe t\u00eb koh\u00ebs. Dhe p\u00ebr k\u00ebt\u00eb ka mjete mjaft t\u00eb mira, \u00e7ka sigurisht \u00ebsht\u00eb nj\u00eb plus i Tableau. Problemi kryesor q\u00eb identifikuam ishin pyetjet SQL shum\u00eb komplekse q\u00eb nd\u00ebrtonte Tableau. Ato lidhen para s\u00eb gjithash me:<\/p>\n<p> \u2014 transpozimin e t\u00eb dh\u00ebnave. Meq\u00eb Tableau nuk ka mjete p\u00ebr transpozimin e dataset-eve, p\u00ebr t\u00eb nd\u00ebrtuar pjes\u00ebn e majt\u00eb t\u00eb dashboard-it me paraqitje t\u00eb detajuar t\u00eb t\u00eb gjith\u00eb KPI-ve, na u desh t\u00eb formonim tabel\u00ebn p\u00ebrmes case. Madh\u00ebsia e pyetjeve SQL n\u00eb BD arriti n\u00eb 120 000 karaktere.<\/p>\n<p><img decoding=\"async\" alt=\"Tableau n\u00eb pakic\u00eb, realisht?\" src=\"\/wp-content\/uploads\/2020\/01\/8fc4d99017ddd604bbabb5ea0a19b38d.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\n \u2014 p\u00ebrzgjedhjen e periudh\u00ebs kohore. Nj\u00eb pyetje e till\u00eb n\u00eb nivelin e BD-s\u00eb merrte m\u00eb shum\u00eb koh\u00eb p\u00ebr kompilim sesa p\u00ebr ekzekutim:<\/p>\n<p><img decoding=\"async\" alt=\"Tableau n\u00eb pakic\u00eb, realisht?\" src=\"\/wp-content\/uploads\/2020\/01\/a9b9cc6ddd6b03c643935d070532728e.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nPra, p\u00ebrpunimi i pyetjes 12 sekonda + 5 sekonda ekzekutim.<\/p>\n<p>Vendos\u00ebm t\u00eb thjeshtonim logjik\u00ebn e llogaritjeve n\u00eb an\u00ebn e Tableau dhe t\u00eb zhvendosnim nj\u00eb pjes\u00eb tjet\u00ebr t\u00eb llogaritjeve n\u00eb pasqyr\u00eb dhe n\u00eb nivelin e BD-s\u00eb. Kjo solli rezultate t\u00eb mira.<\/p>\n<p>Fillimisht b\u00ebm\u00eb transpozimin n\u00eb koh\u00eb reale, e realizuam p\u00ebrmes full outer join n\u00eb faz\u00ebn p\u00ebrfundimtare t\u00eb llogaritjes s\u00eb VIEW, sipas k\u00ebsaj qasjeje t\u00eb p\u00ebrshkruar n\u00eb wiki <noindex><a rel=\"nofollow\" href=\"http:\/\/en.wikipedia.org\/wiki\/Transpose\">Transpose \u2014 Wikipedia, enciklopedia e lir\u00eb<\/a><\/noindex> dhe <noindex><a rel=\"nofollow\" href=\"http:\/\/en.wikipedia.org\/wiki\/Elementary_matrix#Row-addition_transformations\">Elementary matrix \u2014 Wikipedia, enciklopedia e lir\u00eb<\/a><\/noindex>.<\/p>\n<p><img decoding=\"async\" alt=\"Tableau n\u00eb pakic\u00eb, realisht?\" src=\"\/wp-content\/uploads\/2020\/01\/5259995831dc8ae379a34bfe84e52daa.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nPra, krijuam nj\u00eb tabel\u00eb konfigurimi \u2013 matric\u00ebn e transpozimit (21x21) dhe mor\u00ebm t\u00eb gjith\u00eb treguesit n\u00eb ndarje sipas rreshtave.<\/p>\n<p>Ishte:<br \/>\n<img decoding=\"async\" alt=\"Tableau n\u00eb pakic\u00eb, realisht?\" src=\"\/wp-content\/uploads\/2020\/01\/9382ee65a1482cc137a52b5f80c39eeb.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nU b\u00eb:<br \/>\n<img decoding=\"async\" alt=\"Tableau n\u00eb pakic\u00eb, realisht?\" src=\"\/wp-content\/uploads\/2020\/01\/1d6653ec427ce0621b441943f589d860.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nVet\u00eb transpozimi i DB-s\u00eb pothuajse nuk k\u00ebrkonte koh\u00eb. K\u00ebrkesa p\u00ebr t\u00eb gjith\u00eb treguesit p\u00ebr nj\u00eb jav\u00eb vazhdonte t\u00eb ekzekutohej n\u00eb rreth 10 sekonda. Megjithat\u00eb, humbi fleksibiliteti n\u00eb nd\u00ebrtimin e dashboard-it p\u00ebr nj\u00eb tregues t\u00eb caktuar, pra p\u00ebr pjes\u00ebn e djatht\u00eb t\u00eb dashboard-it, ku paraqitet dinamika dhe zb\u00ebrthimi i detajuar i nj\u00eb treguesi specifik. M\u00eb par\u00eb, data mart ekzekutohej p\u00ebr 1-3 sekonda, sepse k\u00ebrkesa b\u00ebhej vet\u00ebm p\u00ebr nj\u00eb tregues, nd\u00ebrsa tani DB-ja gjithmon\u00eb merrte t\u00eb gjith\u00eb treguesit dhe e filtronte rezultatin vet\u00ebm p\u00ebrpara se ta kthente n\u00eb Tableau.<\/p>\n<p>Si rezultat, shpejt\u00ebsia e funksionimit t\u00eb dashboard-it u ul pothuajse 3 her\u00eb.<\/p>\n<p><b>Rezultati:<\/b><\/p>\n<ol>\n<li>5 sek \u2014 parsimi i dashboard-it, vizualizimeve<\/li>\n<li> 15-20 sek \u2014 p\u00ebrgatitja p\u00ebr kompilimin e k\u00ebrkesave me ekzekutimin e parap\u00ebrllogaritjeve n\u00eb Tableau<\/li>\n<li> 35-45 sek \u2014 kompilimi i k\u00ebrkesave SQL dhe ekzekutimi i tyre paralel-sekuencial n\u00eb Hana<\/li>\n<li> 5 sek \u2014 p\u00ebrpunimi i rezultateve, renditja, rillogaritja e vizualizimeve n\u00eb Tableau<\/li>\n<li>Natyrisht, rezultate t\u00eb tilla nuk e k\u00ebnaqnin biznesin dhe ne vazhduam optimizimin.<\/li>\n<\/ol>\n<p><\/p>\n<h3>Faza 2. Minimum logjike n\u00eb Tableau, materializim i plot\u00eb<\/h3>\n<p>\nE kuptonim se ishte e pamundur t\u00eb nd\u00ebrtohej nj\u00eb dashboard me koh\u00eb p\u00ebrgjigjeje prej disa sekondash mbi nj\u00eb data mart q\u00eb punon p\u00ebr 10 sekonda, ndaj shqyrtuam opsionet e materializimit t\u00eb t\u00eb dh\u00ebnave n\u00eb an\u00ebn e DB-s\u00eb posa\u00e7\u00ebrisht p\u00ebr dashboard-in e k\u00ebrkuar. Por u p\u00ebrball\u00ebm me problemin global t\u00eb p\u00ebrshkruar m\u00eb sip\u00ebr \u2014 treguesit jo aditiv\u00eb. Nuk arrit\u00ebm t\u00eb b\u00ebnim q\u00eb, kur ndryshonin filtrat ose nivelet e zgjerimit, Tableau t\u00eb kalonte n\u00eb m\u00ebnyr\u00eb fleksibile midis data mart-eve dhe niveleve t\u00eb ndryshme, t\u00eb parap\u00ebrllogaritura p\u00ebr hierarki t\u00eb ndryshme produktesh (n\u00eb shembull, tre k\u00ebrkesa pa UTE, me UTE1 dhe UTE2 formojn\u00eb rezultate t\u00eb ndryshme). Prandaj mor\u00ebm vendimin ta thjeshtonim dashboard-in, t\u00eb hiqnim dor\u00eb nga hierarkia e produkteve n\u00eb dashboard dhe t\u00eb shihnim sa i shpejt\u00eb mund t\u00eb ishte n\u00eb versionin e thjeshtuar.<\/p>\n<p>Pra, n\u00eb k\u00ebt\u00eb faz\u00eb t\u00eb fundit, nd\u00ebrtuam nj\u00eb depo t\u00eb ve\u00e7ant\u00eb ku vendos\u00ebm t\u00eb gjith\u00eb KPI-t\u00eb n\u00eb form\u00eb t\u00eb transpozuar. N\u00eb an\u00ebn e DB-s\u00eb, \u00e7do k\u00ebrkes\u00eb ndaj k\u00ebsaj depoje ekzekutohet p\u00ebr 0,1\u20130,3 sekonda. N\u00eb dashboard mor\u00ebm rezultatet e m\u00ebposhtme:<\/p>\n<p>Hapja e par\u00eb: 8-10 sekonda<br \/>\n\u00c7do klikim: 6-7 sekonda<\/p>\n<p>Koha q\u00eb shpenzon Tableau p\u00ebrb\u00ebhet nga:<\/p>\n<ol>\n<li>0,3 sek. \u2014 parsimi i dashboard-it dhe kompilimi i k\u00ebrkesave SQL\n<\/li>\n<li>1,5-3 sek. \u2014 ekzekutimi i k\u00ebrkesave SQL n\u00eb Hana p\u00ebr vizualizimet kryesore (niset paralelisht me pik\u00ebn 1)\n<\/li>\n<li>1,5-2 sek. \u2014 renderimi, rillogaritja e vizualizimeve\n<\/li>\n<li>1,3 sek. \u2014 ekzekutimi i k\u00ebrkesave shtes\u00eb SQL p\u00ebr t\u00eb marr\u00eb vlera p\u00ebrkat\u00ebse t\u00eb filtrave (Marka, Divizioni, Qyteti, Dyqani), si dhe parsimi i rezultateve\n<\/li>\n<\/ol>\n<p><\/p>\n<h3>N\u00ebse do ta p\u00ebrmbledhim shkurt<\/h3>\n<p>\nNa p\u00eblqeu mjeti Tableau nga pik\u00ebpamja e vizualizimit. N\u00eb faz\u00ebn e krijimit t\u00eb maketeve shqyrtuam elemente t\u00eb ndryshme t\u00eb vizualizimit dhe i gjet\u00ebm t\u00eb gjitha n\u00eb biblioteka, p\u00ebrfshir\u00eb segmentime komplekse me shum\u00eb nivele dhe waterfall me shum\u00eb driver\u00eb.<\/p>\n<p>Gjat\u00eb zbatimit t\u00eb dashboard-eve me treguesit kryesor\u00eb t\u00eb shitjeve, u p\u00ebrball\u00ebm me v\u00ebshtir\u00ebsi n\u00eb performanc\u00eb q\u00eb ende nuk kemi arritur t\u2019i kap\u00ebrcejm\u00eb. Kaluam m\u00eb shum\u00eb se dy muaj dhe mor\u00ebm nj\u00eb dashboard funksionalisht jo t\u00eb plot\u00eb, me shpejt\u00ebsi reagimi n\u00eb kufijt\u00eb e pranuesh\u00ebm. Nga kjo nxor\u00ebm k\u00ebto p\u00ebrfundime:<\/p>\n<ol>\n<li>Tableau nuk di t\u00eb punoj\u00eb me sasi t\u00eb m\u00ebdha t\u00eb t\u00eb dh\u00ebnave. N\u00ebse n\u00eb modelin origjinal t\u00eb t\u00eb dh\u00ebnave keni m\u00eb shum\u00eb se 10 GB t\u00eb dh\u00ebnash (af\u00ebrsisht 200 mln. X 50 rreshta), at\u00ebher\u00eb dashboard-i ngadal\u00ebsohet ndjesh\u00ebm \u2013 prej 10 sekondash deri n\u00eb disa minuta p\u00ebr \u00e7do klikim. Ne eksperimenti me live-connect dhe me ekstrakt. Shpejt\u00ebsia e pun\u00ebs \u00ebsht\u00eb e krahasueshme.\n<\/li>\n<li>Ka kufizime gjat\u00eb p\u00ebrdorimit t\u00eb disa depozitave t\u00eb t\u00eb dh\u00ebnave (datasets). Nuk ka mund\u00ebsi q\u00eb me mjetet standarde t\u00eb p\u00ebrcaktohen marr\u00ebdh\u00ebniet nd\u00ebrmjet datasets. N\u00ebse p\u00ebrdoren zgjidhje alternative p\u00ebr lidhjen e datasets, kjo ndikon shum\u00eb n\u00eb performanc\u00eb. N\u00eb rastin ton\u00eb, shqyrtuam opsionin e materializimit t\u00eb t\u00eb dh\u00ebnave n\u00eb \u00e7do prerje t\u00eb nevojshme t\u00eb pamjeve dhe realizimin e kalimeve mbi k\u00ebto datasets t\u00eb materializuara duke ruajtur filtrat e zgjedhur m\u00eb par\u00eb \u2014 por kjo doli e pamundur t\u00eb realizohej n\u00eb Tableau.\n<\/li>\n<li>N\u00eb Tableau \u00ebsht\u00eb e pamundur t\u00eb krijohen parametra dinamik\u00eb. Parametrin q\u00eb p\u00ebrdoret p\u00ebr filtrimin e dataset-it n\u00eb extract ose gjat\u00eb live-connect nuk mund ta mbushni me rezultatin e nj\u00eb p\u00ebrzgjedhjeje tjet\u00ebr nga dataset-i ose me rezultatin e nj\u00eb k\u00ebrkese tjet\u00ebr SQL; lejohet vet\u00ebm hyrja native nga p\u00ebrdoruesi ose nj\u00eb konstante.\n<\/li>\n<li>Kufizime q\u00eb lidhen me nd\u00ebrtimin e nj\u00eb dashboard-i me elemente OLAP|tabele p\u00ebrmbledh\u00ebse. <br \/>\nN\u00eb MSTR, SAP SAC dhe SAP Analysis, n\u00ebse shtoni nj\u00eb dataset n\u00eb raport, t\u00eb gjitha objektet n\u00eb t\u00eb lidhen mes tyre si parazgjedhje. N\u00eb Tableau kjo nuk ndodh: lidhjet duhen konfiguruar manualisht. Ndoshta kjo jep m\u00eb shum\u00eb fleksibilitet, por p\u00ebr t\u00eb gjith\u00eb dashboard-et tona kjo \u00ebsht\u00eb nj\u00eb k\u00ebrkes\u00eb e detyrueshme p\u00ebr elementet, prandaj sjell pun\u00eb shtes\u00eb. P\u00ebr m\u00eb tep\u00ebr, n\u00ebse krijoni filtra t\u00eb nd\u00ebrlidhur q\u00eb, p\u00ebr shembull, gjat\u00eb filtrimit sipas rajonit lista e qyteteve t\u00eb kufizohet vet\u00ebm te qytetet e atij rajoni, menj\u00ebher\u00eb kaloni n\u00eb k\u00ebrkesa sekuenciale ndaj DB ose Extract, gj\u00eb q\u00eb e ngadal\u00ebson ndjesh\u00ebm dashboard-in.<\/li>\n<li>Kufizime n\u00eb funksionalitet. Si mbi extract-in, ashtu edhe, aq m\u00eb tep\u00ebr, mbi nj\u00eb dataset nga Live-connect nuk mund t\u00eb b\u00ebni transformime masive. Kjo mund t\u00eb b\u00ebhet p\u00ebrmes Tableau Prep, por kjo do t\u00eb thot\u00eb pun\u00eb shtes\u00eb dhe edhe nj\u00eb mjet tjet\u00ebr q\u00eb duhet m\u00ebsuar dhe mir\u00ebmbajtur. P\u00ebr shembull, nuk mund t\u00eb transpozoni t\u00eb dh\u00ebnat ose t\u00eb b\u00ebni join t\u00eb tyre me vetveten. Kjo z\u00ebvend\u00ebsohet me transformime mbi kolona ose fusha t\u00eb ve\u00e7anta, t\u00eb cilat duhen p\u00ebrzgjedhur me case ose if, dhe kjo krijon SQL query shum\u00eb komplekse, ku baza shpenzon pjes\u00ebn m\u00eb t\u00eb madhe t\u00eb koh\u00ebs duke kompiluar tekstin e query-t. K\u00ebto mungesa fleksibiliteti t\u00eb mjetit na u desh t\u2019i zgjidhnim n\u00eb nivelin e data mart, gj\u00eb q\u00eb \u00e7on n\u00eb nd\u00ebrlikim t\u00eb warehouse-it, ngarkesa shtes\u00eb dhe transformime t\u00eb tjera.\n<\/li>\n<\/ol>\n<p>\nNuk kemi hequr dor\u00eb nga Tableau. Por si mjet i aft\u00eb p\u00ebr t\u00eb nd\u00ebrtuar dashboard-e industriale dhe si zgjidhje me t\u00eb cil\u00ebn mund t\u00eb z\u00ebvend\u00ebsohet dhe digjitalizohet i gjith\u00eb sistemi i raportimit korporativ t\u00eb kompanis\u00eb, Tableau nuk po e konsiderojm\u00eb.<\/p>\n<p>Aktualisht po zhvillojm\u00eb n\u00eb m\u00ebnyr\u00eb aktive nj\u00eb dashboard t\u00eb ngjash\u00ebm n\u00eb nj\u00eb mjet tjet\u00ebr dhe paralelisht po p\u00ebrpiqemi t\u00eb rishikojm\u00eb arkitektur\u00ebn e dashboard-it n\u00eb Tableau p\u00ebr ta thjeshtuar edhe m\u00eb shum\u00eb. N\u00ebse komuniteti do t\u00eb jet\u00eb i interesuar, do t\u00eb ndajm\u00eb rezultatet.<\/p>\n<p>Gjithashtu presim idet\u00eb ose k\u00ebshillat tuaja se si n\u00eb Tableau mund t\u00eb nd\u00ebrtohen dashboard-e t\u00eb shpejta mbi v\u00ebllime kaq t\u00eb m\u00ebdha t\u00eb dh\u00ebnash, sepse ne kemi edhe nj\u00eb faqe interneti ku t\u00eb dh\u00ebnat jan\u00eb shum\u00eb m\u00eb t\u00eb shumta se n\u00eb retail.<br \/>\n<br \/>Burimi: <a content=\"nofollow\" rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/mvideo\/blog\/483656\/\">habr.com<\/a><\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"<p>\u0412\u0440\u0435\u043c\u044f \u043e\u0442\u0447\u0451\u0442\u043d\u043e\u0441\u0442\u0438 \u0432 Excel \u0441\u0442\u0440\u0435\u043c\u0438\u0442\u0435\u043b\u044c\u043d\u043e \u0443\u0445\u043e\u0434\u0438\u0442 \u2014 \u0442\u0440\u0435\u043d\u0434 \u043d\u0430 \u0443\u0434\u043e\u0431\u043d\u044b\u0435 \u0438\u043d\u0441\u0442\u0440\u0443\u043c\u0435\u043d\u0442\u044b \u043f\u0440\u0435\u0434\u0441\u0442\u0430\u0432\u043b\u0435\u043d\u0438\u044f \u0438 \u0430\u043d\u0430\u043b\u0438\u0437\u0430 \u0438\u043d\u0444\u043e\u0440\u043c\u0430\u0446\u0438\u0438 \u0432\u0438\u0434\u0435\u043d \u0432\u043e \u0432\u0441\u0435\u0445 \u0441\u0444\u0435\u0440\u0430\u0445. \u041c\u044b \u0434\u0430\u0432\u043d\u043e \u043e\u0431\u0441\u0443\u0436\u0434\u0430\u043b\u0438 \u0432\u043d\u0443\u0442\u0440\u0438 \u0446\u0438\u0444\u0440\u043e\u0432\u0438\u0437\u0430\u0446\u0438\u044e \u043f\u043e\u0441\u0442\u0440\u043e\u0435\u043d\u0438\u044f \u043e\u0442\u0447\u0451\u0442\u043d\u043e\u0441\u0442\u0438 \u0438 \u0432\u044b\u0431\u0440\u0430\u043b\u0438 \u0441\u0438\u0441\u0442\u0435\u043c\u0443 \u0432\u0438\u0437\u0443\u0430\u043b\u0438\u0437\u0430\u0446\u0438\u0438 \u0438 self-service \u0430\u043d\u0430\u043b\u0438\u0442\u0438\u043a\u0438 Tableau. \u0410\u043b\u0435\u043a\u0441\u0430\u043d\u0434\u0440 \u0411\u0435\u0437\u0443\u0433\u043b\u044b\u0439, \u0440\u0443\u043a\u043e\u0432\u043e\u0434\u0438\u0442\u0435\u043b\u044c \u043e\u0442\u0434\u0435\u043b\u0430 \u0430\u043d\u0430\u043b\u0438\u0442\u0438\u0447\u0435\u0441\u043a\u0438\u0445 \u0440\u0435\u0448\u0435\u043d\u0438\u0439 \u0438 \u043e\u0442\u0447\u0451\u0442\u043d\u043e\u0441\u0442\u0438 \u0413\u0440\u0443\u043f\u043f\u044b \u00ab\u041c.\u0412\u0438\u0434\u0435\u043e-\u042d\u043b\u044c\u0434\u043e\u0440\u0430\u0434\u043e\u00bb, \u0440\u0430\u0441\u0441\u043a\u0430\u0437\u0430\u043b \u043e\u0431 \u043e\u043f\u044b\u0442\u0435 \u0438 \u0438\u0442\u043e\u0433\u0430\u0445 \u043f\u043e\u0441\u0442\u0440\u043e\u0435\u043d\u0438\u044f \u0431\u043e\u0435\u0432\u043e\u0433\u043e \u0434\u0430\u0448\u0431\u043e\u0440\u0434\u0430. \u0421\u043a\u0430\u0436\u0443 \u0441\u0440\u0430\u0437\u0443, \u043d\u0435 [&hellip;]<\/p>\n","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[702],"tags":[],"class_list":["post-55144","post","type-post","status-publish","format-standard","hentry","category-news"],"aioseo_notices":[],"aioseo_head":"\n\t\t<!-- All in One SEO 5.0.2 - aioseo.com -->\n\t<meta name=\"description\" content=\"\u0412\u0440\u0435\u043c\u044f \u043e\u0442\u0447\u0451\u0442\u043d\u043e\u0441\u0442\u0438 \u0432 Excel \u0441\u0442\u0440\u0435\u043c\u0438\u0442\u0435\u043b\u044c\u043d\u043e \u0443\u0445\u043e\u0434\u0438\u0442 \u2014 \u0442\u0440\u0435\u043d\u0434 \u043d\u0430 \u0443\u0434\u043e\u0431\u043d\u044b\u0435 \u0438\u043d\u0441\u0442\u0440\u0443\u043c\u0435\u043d\u0442\u044b \u043f\u0440\u0435\u0434\u0441\u0442\u0430\u0432\u043b\u0435\u043d\u0438\u044f \u0438 \u0430\u043d\u0430\u043b\u0438\u0437\u0430 \u0438\u043d\u0444\u043e\u0440\u043c\u0430\u0446\u0438\u0438 \u0432\u0438\u0434\u0435\u043d \u0432\u043e \u0432\u0441\u0435\u0445 \u0441\u0444\u0435\u0440\u0430\u0445.\" \/>\n\t<meta name=\"robots\" content=\"max-image-preview:large\" \/>\n\t<meta name=\"author\" content=\"Yuri Gagarin\"\/>\n\t<link rel=\"canonical\" href=\"https:\/\/prohoster.info\/sq\/blog\/news\/tableau-v-roznitse-realno\" \/>\n\t<meta name=\"generator\" content=\"All in One SEO (AIOSEO) 5.0.2\" \/>\n\t\t<meta property=\"og:locale\" content=\"sq_AL\" \/>\n\t\t<meta property=\"og:site_name\" content=\"ProHoster | \u041a\u0443\u043f\u0438\u0442\u044c \u043d\u0430\u0434\u0435\u0436\u043d\u044b\u0439 \u0445\u043e\u0441\u0442\u0438\u043d\u0433 \u0434\u043b\u044f \u0441\u0430\u0439\u0442\u043e\u0432 \u0441 \u0437\u0430\u0449\u0438\u0442\u043e\u0439 \u043e\u0442 DDoS, VPS VDS \u0441\u0435\u0440\u0432\u0435\u0440\u044b\" \/>\n\t\t<meta property=\"og:type\" content=\"article\" \/>\n\t\t<meta property=\"og:title\" content=\"\ud83e\udd47Tableau \u0432 \u0440\u043e\u0437\u043d\u0438\u0446\u0435, \u0440\u0435\u0430\u043b\u044c\u043d\u043e? | ProHoster\" \/>\n\t\t<meta property=\"og:description\" content=\"\u0412\u0440\u0435\u043c\u044f \u043e\u0442\u0447\u0451\u0442\u043d\u043e\u0441\u0442\u0438 \u0432 Excel \u0441\u0442\u0440\u0435\u043c\u0438\u0442\u0435\u043b\u044c\u043d\u043e \u0443\u0445\u043e\u0434\u0438\u0442 \u2014 \u0442\u0440\u0435\u043d\u0434 \u043d\u0430 \u0443\u0434\u043e\u0431\u043d\u044b\u0435 \u0438\u043d\u0441\u0442\u0440\u0443\u043c\u0435\u043d\u0442\u044b \u043f\u0440\u0435\u0434\u0441\u0442\u0430\u0432\u043b\u0435\u043d\u0438\u044f \u0438 \u0430\u043d\u0430\u043b\u0438\u0437\u0430 \u0438\u043d\u0444\u043e\u0440\u043c\u0430\u0446\u0438\u0438 \u0432\u0438\u0434\u0435\u043d \u0432\u043e \u0432\u0441\u0435\u0445 \u0441\u0444\u0435\u0440\u0430\u0445.\" \/>\n\t\t<meta property=\"og:url\" content=\"https:\/\/prohoster.info\/sq\/blog\/news\/tableau-v-roznitse-realno\" \/>\n\t\t<meta property=\"og:image\" content=\"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg\" \/>\n\t\t<meta property=\"og:image:secure_url\" content=\"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg\" \/>\n\t\t<meta property=\"og:image:width\" content=\"350\" \/>\n\t\t<meta property=\"og:image:height\" content=\"350\" \/>\n\t\t<meta property=\"article:published_time\" content=\"2020-01-12T21:00:00+00:00\" \/>\n\t\t<meta property=\"article:modified_time\" content=\"2020-02-18T11:03:13+00:00\" \/>\n\t\t<meta property=\"article:publisher\" content=\"https:\/\/www.facebook.com\/prohoster\" \/>\n\t\t<meta property=\"article:author\" content=\"https:\/\/www.facebook.com\/prohoster\" \/>\n\t\t<!-- All in One SEO -->\n\n","aioseo_head_json":{"title":"\ud83e\udd47Tableau n\u00eb retail, a \u00ebsht\u00eb real? | ProHoster","description":"Koha e raportimit n\u00eb Excel po ik\u00ebn me shpejt\u00ebsi \u2014 prirja drejt mjeteve t\u00eb p\u00ebrshtatshme p\u00ebr paraqitjen dhe analiz\u00ebn e informacionit \u00ebsht\u00eb e dukshme n\u00eb t\u00eb gjitha fushat.","canonical_url":"https:\/\/prohoster.info\/sq\/blog\/news\/tableau-v-roznitse-realno","robots":"max-image-preview:large","keywords":"","webmasterTools":{"miscellaneous":""},"schema":null,"og:locale":"sq_AL","og:site_name":"ProHoster | \u041a\u0443\u043f\u0438\u0442\u044c \u043d\u0430\u0434\u0435\u0436\u043d\u044b\u0439 \u0445\u043e\u0441\u0442\u0438\u043d\u0433 \u0434\u043b\u044f \u0441\u0430\u0439\u0442\u043e\u0432 \u0441 \u0437\u0430\u0449\u0438\u0442\u043e\u0439 \u043e\u0442 DDoS, VPS VDS \u0441\u0435\u0440\u0432\u0435\u0440\u044b","og:type":"article","og:title":"\ud83e\udd47Tableau \u0432 \u0440\u043e\u0437\u043d\u0438\u0446\u0435, \u0440\u0435\u0430\u043b\u044c\u043d\u043e? | ProHoster","og:description":"\u0412\u0440\u0435\u043c\u044f \u043e\u0442\u0447\u0451\u0442\u043d\u043e\u0441\u0442\u0438 \u0432 Excel \u0441\u0442\u0440\u0435\u043c\u0438\u0442\u0435\u043b\u044c\u043d\u043e \u0443\u0445\u043e\u0434\u0438\u0442 \u2014 \u0442\u0440\u0435\u043d\u0434 \u043d\u0430 \u0443\u0434\u043e\u0431\u043d\u044b\u0435 \u0438\u043d\u0441\u0442\u0440\u0443\u043c\u0435\u043d\u0442\u044b \u043f\u0440\u0435\u0434\u0441\u0442\u0430\u0432\u043b\u0435\u043d\u0438\u044f \u0438 \u0430\u043d\u0430\u043b\u0438\u0437\u0430 \u0438\u043d\u0444\u043e\u0440\u043c\u0430\u0446\u0438\u0438 \u0432\u0438\u0434\u0435\u043d \u0432\u043e \u0432\u0441\u0435\u0445 \u0441\u0444\u0435\u0440\u0430\u0445.","og:url":"https:\/\/prohoster.info\/sq\/blog\/news\/tableau-v-roznitse-realno","og:image":"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg","og:image:secure_url":"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg","og:image:width":350,"og:image:height":350,"article:published_time":"2020-01-12T21:00:00+00:00","article:modified_time":"2020-02-18T11:03:13+00:00","article:publisher":"https:\/\/www.facebook.com\/prohoster","article:author":"https:\/\/www.facebook.com\/prohoster"},"aioseo_meta_data":{"post_id":"55144","title":null,"description":null,"keywords":null,"keyphrases":null,"primary_term":null,"canonical_url":null,"og_title":null,"og_description":null,"og_object_type":"default","og_image_type":"default","og_image_url":null,"og_image_width":null,"og_image_height":null,"og_image_custom_url":null,"og_image_custom_fields":null,"og_video":null,"og_custom_url":null,"og_article_section":null,"og_article_tags":null,"twitter_use_og":false,"twitter_card":"default","twitter_image_type":"default","twitter_image_url":null,"twitter_image_custom_url":null,"twitter_image_custom_fields":null,"twitter_title":null,"twitter_description":null,"schema":{"blockGraphs":[],"customGraphs":[],"default":{"data":{"Article":[],"Course":[],"Dataset":[],"FAQPage":[],"Movie":[],"Person":[],"Product":[],"ProductReview":[],"Car":[],"Recipe":[],"Service":[],"SoftwareApplication":[],"WebPage":[]},"graphName":"","isEnabled":true},"graphs":[]},"schema_type":null,"schema_type_options":null,"pillar_content":false,"robots_default":true,"robots_noindex":false,"robots_noarchive":false,"robots_nosnippet":false,"robots_nofollow":false,"robots_noimageindex":false,"robots_noodp":false,"robots_notranslate":false,"robots_max_snippet":null,"robots_max_videopreview":null,"robots_max_imagepreview":"large","priority":null,"frequency":null,"local_seo":null,"seo_analyzer_scan_date":null,"breadcrumb_settings":null,"limit_modified_date":false,"reviewed_by":null,"ai":null,"created":"2021-02-28 19:50:02","updated":"2022-10-05 23:10:07","focus_keyword":null,"additional_keywords":null,"truseo_locale":null},"gt_translate_keys":[{"key":"link","format":"url"}],"_links":{"self":[{"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/posts\/55144","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/comments?post=55144"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/posts\/55144\/revisions"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/media?parent=55144"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/categories?post=55144"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/tags?post=55144"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}