Does anyone have an explanation for this?
I have this scenario that pulls ‘assignments’, which are our team member’s monthly hours per project, from our planning software Simplicate into a Google sheet, which is used for a Looker Studio dashboard.
This scenario basically runs every hour, fetches newly created or updated assignments, then either creates or updates rows in the Google Sheet. See below:
Now a team member came to me saying one of their assignments in the LS dashboard was off, as it was in there twice after an update to the amount of hours for that assignment. So instead of updating an existing row, a new one was added.
So I went to Sherlock what was going on here, and here’s what I found. On the given date of the execution, the updated assignment was correctly picked up from Simplicate. The Search module - 59 in the diagram - then did a search to find a row where the ID of the assignment matched the one from Simplicate (Red box). It matched a row that had a completely different ID! (Yellow box).
This strikes me as really odd. Some things that I thought about:
- Is it doing a fuzzy match? Doesn’t seem to make sense…
- Is there a character limit to matching the search?
It gets funnier - even though there is a match and it then flows down the Update path, it doesn’t actually update that row, but proceeds to create a new one.
Anyone know what’s happening here?