Identifying change to be made

[ChrisDL]

I have a workflow that compares two lists - list A and list B. List A is the master list which must always be correct.

The output at the moment looks like this

Name	Industry	Plan	Result
A	Accommodation And Food Services	Starter	Not in List A
B	Unknown	Premium	Not in List A
C	Unknown	Premium	Not in List A
D	Wholesale Trade	Premium	Not in List A
D	Wholesale Trade	Standard	Not in List B
E	Professional, Scientific And Technical Services	Premium	Not in List B
E	Professional, Scientific And Technical Services	Starter	Not in List A

A, B and C need to be added to List A while D and E need the Industry or Plan fields (or both) currently in List A to be updated with the information in List B.

The type of output I want is something like this - but this is only a suggestion

Name	Industry	Plan	Result
A	Accommodation And Food Services	Starter	Not in List A
B	Unknown	Premium	Not in List A
C	Unknown	Premium	Not in List A
D	Wholesale Trade	Standard	Change Plan to Premium
E	Professional, Scientific And Technical Services	Starter	Change Plan to Premium

I have to account for two possibilities not in this example:

• Both the Industry and the Plan need a change
• That the record needs deleting from list A because it is has been removed from list B

Example data for the above attached and any suggestions gratefully received!

[mot]

Hi @ChrisDL,

I am not sure I understand the logic clearly. For instance, there are 2 Es in the first table; one not in List A and the other not in List B. Could you add more clarification to the logic? Thanks! 

[ChrisDL]

Hi @mot 

Thanks for looking at my query - apologies that I was not clear.

In the table (and the input data) I have used a simple join earlier in the workflow to compare the two lists so "Not in list A" means that there is no exact match (for name and plan and industry) in List A compared to List B (and vice versa) - so if the name is in both lists and plan or industry (or both) is different between list A and list B it would always show up twice

Hopefully that makes sense