Rreiterating what Karen stated. In addition I feel like i will lose all my current exports and will need to rebuild the all. I really don't understand why the people designing this unified view can't comprehend what the power users currently do and the issues this could cause
I'm not sure what this idea is specifically requesting, but I'll add my use case here.
Many organizations have a generic export and attach different queries to it. For example, a single "mailing list" export that can be used with many different queries. There is concern that the proposed "single row query" will not allow for that possibility, which would actually result in MORE work for customers. I don't want to reconfigure the output fields for certain exports just because they are connected to different queries.
Rreiterating what Karen stated. In addition I feel like i will lose all my current exports and will need to rebuild the all. I really don't understand why the people designing this unified view can't comprehend what the power users currently do and the issues this could cause
I'm not sure what this idea is specifically requesting, but I'll add my use case here.
Many organizations have a generic export and attach different queries to it. For example, a single "mailing list" export that can be used with many different queries. There is concern that the proposed "single row query" will not allow for that possibility, which would actually result in MORE work for customers. I don't want to reconfigure the output fields for certain exports just because they are connected to different queries.