-
-
Notifications
You must be signed in to change notification settings - Fork 3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Importing - "Do Not Import" disappears #7996
Comments
Hi, I can confirm this issue exists (And always has). I just took a look at it, it's going to be a bit more complicated to fix than I thought it would be given how the various parts and pieces talk to each other. Let me think on it a bit and see what I can come up with. |
Is this still relevant? We haven't heard from anyone in a bit. If so, please comment with any updates or additional detail. |
This is still relevant
…On Thu, Jul 2, 2020, 22:33 stale[bot] ***@***.***> wrote:
Is this still relevant? We haven't heard from anyone in a bit. If so,
please comment with any updates or additional detail.
This issue has been automatically marked as stale because it has not had
recent activity. It will be closed if no further activity occurs. Don't
take it personally, we just need to keep a handle on things. Thank you for
your contributions!
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#7996 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAKJ7E7PKHUQBPEJZLH3GULRZVGRFANCNFSM4MR7LK4Q>
.
|
Okay, it looks like this issue or feature request might still be important. We'll re-open it for now. Thank you for letting us know! |
Is this still relevant? We haven't heard from anyone in a bit. If so, please comment with any updates or additional detail. |
This is still relevant
…On Wed, Sep 2, 2020, 01:10 stale[bot] ***@***.***> wrote:
Is this still relevant? We haven't heard from anyone in a bit. If so,
please comment with any updates or additional detail.
This issue has been automatically marked as stale because it has not had
recent activity. It will be closed if no further activity occurs. Don't
take it personally, we just need to keep a handle on things. Thank you for
your contributions!
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#7996 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAKJ7E7SSCZ6YZ3VC2C3EFDSDXOWJANCNFSM4MR7LK4Q>
.
|
Okay, it looks like this issue or feature request might still be important. We'll re-open it for now. Thank you for letting us know! |
Is this still relevant? We haven't heard from anyone in a bit. If so, please comment with any updates or additional detail. |
This issue still exists in current version, just ran into it, which makes importing all but useless without having to hand edit the import CSV file. |
Okay, it looks like this issue or feature request might still be important. We'll re-open it for now. Thank you for letting us know! |
Please confirm you have done the following before posting your bug report:
Describe the bug
When importing a file, the option to "Do Not Import" a field appears, until you choose an Import Type. This makes it so this functionality isn't usable, and instead fields must be removed from the source import file.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The "Do Not Import" option should remain, allowing a user to exclude a field from importing
Screenshots
Server (please complete the following information):
Desktop (please complete the following information):
Error Messages
Nothing in the DebugBar or browser console
The text was updated successfully, but these errors were encountered: