Journey Orchestrator Query Builder Field Mapping

It would be nice if you didn’t have to remap all of the fields if you change/rerun the query. in the step one.  I understand some warnings/alerts if those fields mapped are no longer valid, but this is a pain when you have many fields you are working with.



Recreating contact queries each time is definitely time consuming. 

Thanks for sharing. We are working on improving Journey Orchestrator experience and will definitely consider this as well.