Just trying the new experience while creating datasets. This new experience seems to have a bug when displaying and storing the data in the backend and ignores all the nulls in the data (keeps the nulls at the end and not in the correct columns)
EDIT (Just replacing the screenshot with sample data for better visual explanation)
So Original data in a database stored as following
Column 1
Column 2
Column 3
data1
data2
data3
data1
null
data3
null
null
data3
Then after using the new experience to create new dataset, the values get shifted as bellow:
Column 1
Column 2
Column 3
data1
data2
data3
data1
data3
null
data3
null
null
With the legacy version I have no issue in here and the data in the database tables is fine as confirmed
@drpeter@WLS-Luis@WLS-Luis Could one of you take a look at this when you are back from the holiday? Or open to any feedback from our Community Experts as well.
Welcome to the Quick Community! Based on your post and previous posts with similar behavior, this does seem to be a current bug within the new experience. I will make sure to keep this post marked as âerrorâ so that someone from the AWS Team may potentially address this issue.
Just checking back in since we havenât heard from you in a bit. I wanted to see if the guidance shared earlier helped resolve your question, or if you found a solution in the meantime. Moreover, if you are still experiencing the bug, then i would recommend submitting a support ticket. Submitting a support ticket will allow the support team to further investigate your situation and hopefully provide any findings to what youâre experiencing. To submit a support ticket, please refer to this resource (Case management - AWS Support).
If you still have any additional questions related to your initial post, feel free to share them. Otherwise, any update youâre able to provide within the next 3 business days would be helpful for the community.
I wanted to follow up on the bug I reported earlier. I may have missed any guidance or expectations you had regarding next steps, so please let me know if thereâs a specific process I should be following.
Iâve identified and documented the issue, and Iâm happy to create a formal ticket if that would be helpful for tracking and resolution.
Moving forward, it would be great to have visibility into progress updates when someone is actively working on reported bugs. This would allow me to conduct timely testing and provide confirmation once fixes are implemented.
Please let me know how youâd prefer to handle this and any future bug reports.
This post has an âerrorâ tag attached to it which helps visibility to the Quick teams regarding the bug. Sometimes submitting a support ticket can help expedite the process, but it is not a guarantee.
I completely understand your sentiment towards visibility into progress updates. I am not an AWS employee so I cannot speak on what AWS can offer in regard to that but submitting a support ticket does offer additional progress updates as your case is being worked on. I think for any future bugs, itâll depend on the size of the issue. Larger bugs are best handled through a support ticket, while smaller issues or questions can be posted here in the community. And if youâre ever unsure which route to take, feel free to ask here in the community first and we can help point you in the right direction.
Just checking back in since we havenât heard from you in a bit. I wanted to see if the guidance shared earlier helped resolve your question. Moreover, did you submit a support ticket? If so, if your support ticket uncovered any findings, please feel free to share them!
If you still have any additional questions related to your initial post, feel free to share them. Otherwise, any update youâre able to provide within the next 3 business days would be helpful for the community.
Since I havenât received any further updates from you, Iâll treat this inquiry as complete for now. If you have any additional questions, feel free to create a new post in the community and link this discussion for context.