It sounds like a calculated field should be created before to take out the Loc1234 origins then, place the calculated field on the filter shelf. If you post some sample data that looks similar to yours I can show you.
The problem I was running into was that the Origin has a Zip Code linked to it and by filter on a single Origin I lose that link between the Origin Zip and Destination Zip that make up each Path ID (this is the line that's mapped).
To fix this I parsed out the Origin from the Path ID. This allows me to roll up all of the Paths starting with a selected Origin and map both the Origin and Destination Zips on the map. Since the Origin isn't the value being mapped I can use it as an aggregate filter.
Sorry I don't have any examples to share, the data's confidential
Thank you so much for the assistance!