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.
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.
Please provide sample data that fully covers your issue.
Please show the expected outcome based on the sample data you provided.
The examples above cover exactly the scenario I have, it is unlikely that all workers will return to FLOTEL because the report starts at 0:00 a.m. and ends at 11:59 p.m. and work shifts are from 7:00 a.m. to 7 p.m. and 7 p.m. to 7 a.m. In cases where the worker goes from FLOTEL to PLATFORM and there is no return record, the output may be null or 0.
But please don't get hung up on the calculation itself or logic, I just need some help to the point of having the two columns with the departure and return times of the PLATFORM, from then on I know how to proceed with all the particularities. In the calculation I will check if the next line has the same worker record as the current line, if so it does the duration calculation, otherwise it returns null or 0.
Your problem is much more fundamental. You are trying to use Power BI for something it is not designed for - divining the relationship between events based on potentially incomplete sampling data.
In the real world they may not swipe in or swipe out reliably, and you are left with scenarios where they left the building that they never entered (mysterious) or they entered and never left (troublesome) and all kinds of other scenarios. That's just not something Power BI can help you with.
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.