1
00:00:00,080 --> 00:00:04,143
Two versions of a ticket list contain the same four IDs

2
00:00:04,143 --> 00:00:05,990
but in different row orders.

3
00:00:05,990 --> 00:00:10,053
A row-by-row comparison would accuse almost everything of changing.

4
00:00:10,053 --> 00:00:14,486
We will match by Ticket ID and show that only T-101

5
00:00:14,486 --> 00:00:17,071
and T-102 have different status values.

6
00:00:17,671 --> 00:00:21,816
Import the two fictional CSVs into a private Google Sheet with

7
00:00:21,816 --> 00:00:23,699
tabs named Old and New.

8
00:00:23,699 --> 00:00:27,843
Read the Old statuses first, then notice that the New tab

9
00:00:27,843 --> 00:00:30,857
starts with T-104 rather than T-101.

10
00:00:30,857 --> 00:00:35,002
The source rows remain intact while a helper result is calculated

11
00:00:35,002 --> 00:00:36,509
on the Old tab.

12
00:00:37,109 --> 00:00:41,335
On Old, XLOOKUP uses A2 as the ticket key and searches

13
00:00:41,335 --> 00:00:46,331
the New ID column, then returns the status from the same New row.

14
00:00:46,331 --> 00:00:48,636
This avoids comparing unrelated row positions.

15
00:00:48,636 --> 00:00:53,247
The four-row lookup and result ranges must stay aligned when the

16
00:00:53,247 --> 00:00:54,784
formula is filled downward.

17
00:00:55,384 --> 00:01:01,639
T-101 changes from Open to Closed, and T-102 changes from Waiting to Assigned.

18
00:01:01,639 --> 00:01:04,141
The formula should label both Changed.

19
00:01:04,141 --> 00:01:09,562
T-103 stays Open and T-104 stays Closed, so they should be

20
00:01:09,562 --> 00:01:12,899
Same even though their physical row positions moved.

21
00:01:13,499 --> 00:01:17,334
Ignore the worksheet row order and write each ID with its

22
00:01:17,334 --> 00:01:18,729
old and new status.

23
00:01:18,729 --> 00:01:20,821
Two pairs differ and two match.

24
00:01:20,821 --> 00:01:23,611
This manual map agrees with the formula output.

25
00:01:23,611 --> 00:01:27,446
If all four appear different, you likely compared row numbers instead

26
00:01:27,446 --> 00:01:29,190
of using the ticket key.

27
00:01:29,790 --> 00:01:34,486
This exercise has one occurrence of every ID in both tabs.

28
00:01:34,486 --> 00:01:39,609
In a real comparison, a missing ID can produce #N/A and

29
00:01:39,609 --> 00:01:43,878
a duplicate ID can make the first returned status misleading.

30
00:01:43,878 --> 00:01:49,001
Investigate those conditions separately instead of labeling them as ordinary status changes.
