-
Notifications
You must be signed in to change notification settings - Fork 76
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
[GUI-BUG] - Incorrect Data displayed in Query Test Result #821
Comments
Hello, @mrcdsouza Thank you for reporting a bug. Cheers |
This case has been marked as 'to-be-closed', since it has no activity for the 3 days. |
This case has been closed, since it has no activity for the last 6 days. Feel free to reopen it, if you need more help. |
@mrcdsouza |
Thank you for the fix and for your great data migration application.
[A black and green logo Description automatically generated]<http://www.ptc.com/>
Carlton D’Souza
Director – Solution Demo Engineering
(845) 262-3468
***@***.******@***.***>
ptc.com<http://www.ptc.com/>
From: Haim Knokh ***@***.***>
Date: Tuesday, August 13, 2024 at 10:03 AM
To: forcedotcom/SFDX-Data-Move-Utility ***@***.***>
Cc: D'Souza, Carlton ***@***.***>, Mention ***@***.***>
Subject: Re: [forcedotcom/SFDX-Data-Move-Utility] [GUI-BUG] - Incorrect Data displayed in Query Test Result (Issue #821)
@mrcdsouza<https://github.com/mrcdsouza>
This issue has been fixed since v4.8.1
—
Reply to this email directly, view it on GitHub<#821 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ANJZQ5ICXAMRF62ZDSEGTXTZRIGZBAVCNFSM6AAAAABKYEITSKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEOBWGMZTQMJQHE>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
Hello. This case is now considered resolved, and I am closing it for now. If you have any additional questions or concerns, please don't hesitate to reach out. Regards. |
In the GUI, for number fields Level__c and Order_By__c, a Date Value is displayed instead of a integer:
here is the data in SOQLXplorer:
The text was updated successfully, but these errors were encountered: