Our organisation manually inputs batches which do not fit templates (or its not worth creating them for the few per batch - it would make it too time consuming going in and out) so we need to be able to look up headers.
Losing the ability to manually map the fields means that any import user will need to know which fields are the right ones when they set up the import; even as someone who imports a few times a week I still need to look up headers sometimes. This will take more time to prepare an import (especially if we also don't have templates). Being able to manually map the fields -- to select from the menu like in RE7 -- will save a lot of time and be a lot more user frindly.
I believe it would save time rather than having to cancel the import, open the import file again and change the headers and additionally on some imports there are certain fields which are the same data but named differently depending on what import you are doing.
Our organisation manually inputs batches which do not fit templates (or its not worth creating them for the few per batch - it would make it too time consuming going in and out) so we need to be able to look up headers.
Losing the ability to manually map the fields means that any import user will need to know which fields are the right ones when they set up the import; even as someone who imports a few times a week I still need to look up headers sometimes. This will take more time to prepare an import (especially if we also don't have templates). Being able to manually map the fields -- to select from the menu like in RE7 -- will save a lot of time and be a lot more user frindly.
Manual mapping is absolutely essential for us
I believe it would save time rather than having to cancel the import, open the import file again and change the headers and additionally on some imports there are certain fields which are the same data but named differently depending on what import you are doing.
Manual mapping is essential.