Hello... PowerAutomate rookie here. I'm having an issue where an Update Items flow I have running is working correctly. However, I made a change in the way end users can edit data in our PowerApp, and now the flow is overtaking their edits because it's based on anything changing in the reference list. The catch is that I can't seem to figure out how to ignore 2 specific columns in the original flow. I've tried creating a view that doesn't contain the 2 specific columns and having the flow run with the List Columns by View set to the created view... but it doesn't work. Can someone please guide me in what I'm doing wrong?
Current Flow
As you can see I'm looking to see if an item is updated in my Contact List, and if so, the flow will update the referenced All Asset List for the affected updated Contact. You can also see where I attempted to create a view named "Basic" where I specifically left out the two columns I want the flow to ignore which is PREVIOUS AUDIT & NEXT AUDIT DUE (screen cap below)... but it didn't work.


Explanation/Issue
The original flow is intended to monitor the Contact List, and should the condition apply, update any record in my All Asset List for the respective Contact (Holder) if their contact record is updated in the Contact List. However, there are two columns I added after I set up the flow that are needed to notify me when a Contact/Holder's next Audit is due. The problem is after I complete an audit this separate flow runs and updates these 2 columns in my Contact List which makes the flow I'm referencing now run because an item in the list has been modified. When this flow runs, it updates the Location on my All Asset List for the records for that Contact/Holder based on what's listed in their contact record. However, I don't want it to because the respective Contact's can now manually edit the location's of their assets based on the people they lend them to. This creates a situation where they could have 100 different items in 30 separate physical locations, but the records are reset to their default location. You can see this would be a nightmare to fix.
The Bottom Line
If the first When an item or a file is modified action would ignore these two columns (PREVIOUS AUDIT & NEXT AUDIT DUE) altogether, my problem would be solved.
Can someone please let me know if this can be resolved in the current flow, or do I need to reinvent the wheel?