You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Make sure to read the troubleshooting section before creating an issue
[ v] I've read the common issues and the one I'm about to create is not one of those documented.
[v ] I've read the release note and the one I'm about to create is not already fixed.
Describe the bug
Query of a junction object returns multiple incorrect records that mostly don't exist.
The following query for example returns 1606 records, but running the same SOQL in the developer's console only returns 265 records:
select ServiceAppointment.Latitude, ServiceAppointment.Longitude, ServiceAppointment.AppointmentNumber, ServiceResourceId, ServiceAppointment.SchedStartTime
from AssignedResource
where ServiceAppointment.OptContext__c like 'CO CRIS 2%'
and ServiceAppointment.SchedStartTime > 2025-08-11T00:00:00.209-06:00
and ServiceAppointment.SchedStartTime < 2025-08-12T00:00:00.209-06:00
order by ServiceAppointment.AppointmentNumber, ServiceAppointment.SchedStartTime
The results includes the following entries for ServiceAppointment record "SA-15705021" , some for linked record identified by ServiceResourceId 0Hn3j000000TYg2CAG which is a duplicate and two other references to other ServiceResource records:
hi @tprouvot , per my comments in the description the dev console returns the correct 265 records, vs. 1606 returned in the inspector. This seems like a fairly severe issue IMHO.
@tprouvot, interestingly I just ran the same SOQL again and it now returns the correct number of records.
Has anyone made any fixes just now?
tprouvot
changed the title
Query of junction object returns multiple incorrect records
[data-export] Query of junction object returns multiple incorrect records
Jan 13, 2025
Hi @MosheZuchmir,
You did not mentioned the version you were using when you opened the issue, is it the 1.25 ?
Are you using the main or beta version ?
I updated the % release of the new version this morning so you may have been upgraded to the new version (chrome should have ask you for granting permission for a new domain)
Make sure to read the troubleshooting section before creating an issue
Describe the bug
Query of a junction object returns multiple incorrect records that mostly don't exist.
The following query for example returns 1606 records, but running the same SOQL in the developer's console only returns 265 records:
select ServiceAppointment.Latitude, ServiceAppointment.Longitude, ServiceAppointment.AppointmentNumber, ServiceResourceId, ServiceAppointment.SchedStartTime
from AssignedResource
where ServiceAppointment.OptContext__c like 'CO CRIS 2%'
and ServiceAppointment.SchedStartTime > 2025-08-11T00:00:00.209-06:00
and ServiceAppointment.SchedStartTime < 2025-08-12T00:00:00.209-06:00
order by ServiceAppointment.AppointmentNumber, ServiceAppointment.SchedStartTime
The results includes the following entries for ServiceAppointment record "SA-15705021" , some for linked record identified by ServiceResourceId 0Hn3j000000TYg2CAG which is a duplicate and two other references to other ServiceResource records:
_ ServiceAppointment ServiceAppointment.Latitude ServiceAppointment.Longitude ServiceAppointment.AppointmentNumber ServiceAppointment.SchedStartTime ServiceResourceId [AssignedResource] [ServiceAppointment] 39.541324 -104.819348 SA-15705021 2025-08-11T16:42:00.000+0000 0Hn3j000000TYbdCAG [AssignedResource] [ServiceAppointment] 39.541324 -104.819348 SA-15705021 2025-08-11T16:42:00.000+0000 0Hn3j000000TYjbCAG [AssignedResource] [ServiceAppointment] 39.541324 -104.819348 SA-15705021 2025-08-11T16:42:00.000+0000 0Hn3j000000TYg2CAG [AssignedResource] [ServiceAppointment] 39.541324 -104.819348 SA-15705021 2025-08-11T16:42:00.000+0000 0Hn3j000000TYg2CAG [AssignedResource] [ServiceAppointment] 39.541324 -104.819348 SA-15705021 2025-08-11T16:42:00.000+0000 0Hn3j000000TYg2CAG [AssignedResource] [ServiceAppointment] 39.541324 -104.819348 SA-15705021 2025-08-11T16:42:00.000+0000 0Hn3j000000TYjbCAG
To Reproduce
Steps to reproduce the behavior: Per the above, likely with any junction object.
Expected behavior
The above DOQL should have returned a single record for each ServiceAppointment and ServiceResource.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: