You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Some sites use the importer regularly as part of a workflow e.g. to update subscription data across many subscribers every week. Having to manually set the CSV mapping every time you import a file is error prone, especially for columns which are imported as custom fields on users or subscriptions.
The best solution I think would be if the mapping would persist from import to import. Alternately, it would be slightly less convenient but still workable, if there was a filter available to customize the CSV mapping. Either should reduce the amount of human error that can happen across multiple imports.
The text was updated successfully, but these errors were encountered:
Some sites use the importer regularly as part of a workflow e.g. to update subscription data across many subscribers every week. Having to manually set the CSV mapping every time you import a file is error prone, especially for columns which are imported as custom fields on users or subscriptions.
The best solution I think would be if the mapping would persist from import to import. Alternately, it would be slightly less convenient but still workable, if there was a filter available to customize the CSV mapping. Either should reduce the amount of human error that can happen across multiple imports.
The text was updated successfully, but these errors were encountered: