[COMPASS-3960] Insert modal for int64 values in Data Explorer doesn't accept some values, changes number Created: 01/Feb/19 Updated: 29/Oct/23 Resolved: 19/Oct/20 |
|
| Status: | Closed |
| Project: | Compass |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 1.23.0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Marie Atterbury | Assignee: | Unassigned |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Documentation Changes: | Not Needed |
| Description |
|
Some values cannot be inserted as int64 numbers in the Insert Document modal in the Atlas UI. They're dynamically changed to a different value in the submission form before the insert can be submitted. This could cause customers to unknowingly insert incorrect data into their projects via the UI. Steps to reproduce (or see this screen recording): Workaround: |
| Comments |
| Comment by Rhys Howell [ 19/Oct/20 ] |
|
Looks like this was fixed, 1.23.0 has an update that allows for searching for these number long values. |
| Comment by Jonathan Balsano [ 12/Nov/19 ] |
|
This appears to be a bug we've inherited from Compass. Moving |
| Comment by Rez Khan (Inactive) [ 07/Nov/19 ] |
|
Thanks! Will triage it next week and let you know status. |
| Comment by Melissa Plunkett [ 07/Nov/19 ] |
|
Program Management Note
|
| Comment by Melissa Plunkett [ 07/Nov/19 ] |
|
rezwan.khan fyi this definitely appears to be a bug. Moving over to CLOUDP for triage. |
| Comment by Noah Skelton (Inactive) [ 07/Nov/19 ] |
|
I've got a customer on Intercom with this exact issue, and have repro'd on my end. Any int64 number inserted from data explorer will get converted to an int32. |
| Comment by Melissa Plunkett [ 01/Feb/19 ] |
|
rezwan.khan, possible Data Explorer bug. |