I’m running into an issue with the new import UI where it will show the correct value of a Custom Field within the preview but once the import begins it maps the field to the drop-down selection that is one after the correct selection. In this instance I am mapping data to a Custom Field called “Contract Year”. In the image below you can see the value of that field is previewing as “Year 8” which is correct. However, when imported the value shows to be “Year 9” as shown below.
I attempted this twice and got the same results. I am also finding that the pop-up in the bottom left never completes once all the tasks have been imported.
No Pop-up Updates:
Browser version: Google Chrome is up to date - Version 76.0.3809.132 (Official Build) (64-bit)
Thanks for the report @LEGGO,
Would you mind sharing your CSV file and the URL of your Test project by DM to help me investigate this further?
Looking forward to your reply!
Hi @LEGGO and thanks for your patience! I just tried to reproduce the issue with the CSV file you DMed me, and the data I’m seeing in the test project I created for the occasion is correct (see screenshot below), so I’m not sure what’s happening there! I’ve gone ahead and filed a bug with our Product team to investigate this further and I’ll keep you posted as soon as I have an update!
@LEGGO, so our team just came back to me, and something caught up their attention. On you screenshots, the “Contract Year” custom field has no field option color, which doesn’t match the preview. In order to continue investigating, could you answer these few questions?
- Is this a dropdown custom field?
- If so, what field options have you set up?
- Are you creating a new custom field for Contract Year or using an existing organizational one?
- Any chance you have modified the options for the custom field after importing?
Looking forward to your reply!
@Marie thanks for responding. I just got a chance to try this again and got the same result. I wasn’t able to see a screenshot in your previous reply however.
AH! Nice catch by the team (noticing the lack of colors)
To answer your questions:
- The field options are 2010-2030 and Year 2-25 for a total of 45 individual options. See screenshot below. Perhaps that is the issue and I have too many options for a Custom Field?!?
- Existing organization one (the best way )
- No modifications. I thought perhaps that was the issue too, as if the Field option or the CSV cell had a space in reference name. Doesn’t appear to the be the case either.
Thanks for the quick reply @LEGGO, we’re into it and I’ll make sure to keep you in the loop as soon as I have an update
So sorry for the trouble, but would you be able to forward us a screencast by any chance?
Loom is a great app for video screencasts: https://www.useloom.com/
** Browse in private - Computer - Google Chrome Help
** Chrome DevTools - Chrome Developers
Try to include the entire browser window, including URL bar, in the video screencast.
Also, is this consistently happening? Could you also check if you’re able to reproduce with another project?
THANK YOU so much for your help and patience with this!
I hope this gets you what you need. I ran another test with a different field option and it did the same thing - selected the “next” option instead of the one identified, e.g. selecting 2010 instead of 2019 and Year 9 instead of Year 8.
Cheers @LEGGO, really appreciate it.
I’ve removed the screencast from the thread to preserve your info, but I’ve forwarded it to our team! I’ll keep you posted as soon as I hear from them!
@Marie, for that it is worth, if I don’t browse in the Organizational Custom Field prior to importing (thus it creates a new Custom Field with only 1 field option) then it DOES NOT list the Contract Year as “Year 9”. I do believe this behavior has something to do with the number of Custom Field options - causing an unexpected offset when importing the data.
Good morning, @Marie! Just checking in to see if the team has uncovered what is causing this behavior. Have a great day!
No news yet @LEGGO, but I’ll ping the bug
No worries or immediate rush, @Marie. Just checking in. Have a great day!
Good news @LEGGO, our team has isolated the issue and should be pushing a fix within the next couple of days Will update you here as soon as the fix is live!
The fix is live, so this issue should now be resolved! @LEGGO, don’t hesitate to comment on this thread if you run again into this issue! Thanks again for your help and cooperation!