Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hola a todos,
Eh trabajado durante dos años con qlik sense y me encuentro en un dilema, tengo una aplicación que se conecta a las bases de datos de la empresa y me brinda la información actualizada a la fecha en la que se realiza la recarga (TABLAS ACUMULATIVAS), luego esa data la combino y creo una tabla que brida ciertos indicadores a la fecha de corte.
Ahora bien, lo que quiero es saber si es posible o no, realizar algún tipo de comando/formula/codigo, que me permita crear en una tabla o archivo (para consulta) en donde se almacenen los datos de la ultima recarga realizada, y que en la "original" se muestren los datos "nuevos" o actualizados para poder realizar comparaciones entre estos.
Esto dejando claro que la data de donde tomo la información solo guarda nueva información no registros por fechas.
//
Hello everyone,
I have worked for two years with qlik sense and I find myself in a dilemma, I have an application that connects to the company's databases and gives me updated information on the date on which the recharge is made (ACCUMULATIVE TABLES), then I combine that data and create a table that provides certain indicators to the cut-off date.
Now, what I want is to know if it is possible or not, to carry out some type of command/formula/code, which allows me to create a table or file (for consultation) where the data of the last reload carried out is stored, and that the "new" or updated data is shown in the "original" so that comparisons can be made between them.
This makes it clear that the data from which I take the information only saves new information, not records by dates.
Hi, the first thought that comes to mind would be to store your data/table to separate qvd/csv with date mark or just called 'last reload' after your app reload. You can add some simple IF THEN ELSE script if needed, play with realoadtime<=today flags, qvd file time comparison and so on, but new logic could be so that first you load table from your 'yesterday qvd' (I assumed here you refresh app each day). Then you load your new, today's data. At this point you have your yesterday and today data in one app, you can make comparison or something. At last, you store your new data to qvd for tomorrow (if, for example, data differs from yesterdays). How Store function works or script how to load last qvd I believe you can easily find in qlik community or qlik help, but everything depends on way you will choose.
Hello,
Have you had a look at Native Path:( *** ) System error:( *** ) - Qlik Community - 1717101 ?
Cheers,
Albert
Hi, the first thought that comes to mind would be to store your data/table to separate qvd/csv with date mark or just called 'last reload' after your app reload. You can add some simple IF THEN ELSE script if needed, play with realoadtime<=today flags, qvd file time comparison and so on, but new logic could be so that first you load table from your 'yesterday qvd' (I assumed here you refresh app each day). Then you load your new, today's data. At this point you have your yesterday and today data in one app, you can make comparison or something. At last, you store your new data to qvd for tomorrow (if, for example, data differs from yesterdays). How Store function works or script how to load last qvd I believe you can easily find in qlik community or qlik help, but everything depends on way you will choose.
Thanks, I actually looked for the store function but i couldn't made that works, when i reloaded the data show me the next error
Hello,
Have you had a look at Native Path:( *** ) System error:( *** ) - Qlik Community - 1717101 ?
Cheers,
Albert
Hi, yes i did.
And what i found was that on the store function you should use a [lib://AttachedFiles/ as direction to store de qvd/csv document and i was using a server folder direction.
Thank you all so much.