Forum Discussion
Loading data too large
Cases where the worker may not have registered or there may have been a failure in the entry or exit registration will be validated, this logic and the calculation I already have. Remember that the problem I was facing was the slowness and the large number of bytes that were being loaded when loading the data because of the use of readings in subsequent rows in the same query.
I've already managed to resolve the situation. What I did was duplicate the query, then I added a column with a 1-based index to the first query and a 0-based index to the second query and I merged the queries based on the indexes, taking only the "Movement Time" column and that's it.
To do this, I was duplicating the column and making all the values move to the previous row,Your sample data doesn't support this. What is the expected outcome for NAME_247 ?
Remember that Power Query does not guarantee any sort order.
Your sample data doesn't support this. What is the expected outcome for NAME_247 ?This is a case in which the worker will only return the next day, that is, his/her return will only be recorded in the next report. I only gave you examples covering three days, but this case may happen in the last report received, after all, we have night shifts that start at 7:00 pm and end at 7:00 am.