Forum Discussion
Salesforce Connection - Missing Objects
Hi Anonymous,
I know this is an old thread, but the screenshot gives an important clue. It looks like Power Query is trying to call ServiceAppointment through /services/data/v29.0/... and getting 404 Not Found.
For this specific object, I would first check the M query in Advanced Editor, not only the Salesforce connection dialog. ServiceAppointment is available only in newer Salesforce API versions, so an old API path can make the object appear missing.
For the native Salesforce Objects connector path, I would try:
- Clear the old Salesforce permissions in Power BI Desktop and reconnect.
- Rebuild the Salesforce Objects query from scratch.
- In Advanced Editor, explicitly set a supported API version, for example:
Source = Salesforce.Data("https://login.salesforce.com/", [ApiVersion = 54.0])
- Confirm that the Salesforce user has API Enabled permission.
- Confirm the user has object-level access to ServiceAppointment.
- If ServiceAppointment comes from Field Service or Scheduler in your org, confirm that the required product access and permission sets are assigned.
- Use a supported Salesforce production or custom domain URL, not a Lightning URL.
If the object is still missing or the native connector keeps giving inconsistent metadata, another option is to test a Salesforce-side connector. One alternative is Power BI Connector for Salesforce by Metrica Software, available on Salesforce AgentExchange / AppExchange: https://appexchange.salesforce.com/appxListingDetail?listingId=31526f0e-abd8-4cb5-bd1a-3bd56b5c0577
With this approach, you create the data source inside Salesforce, select the Salesforce objects and fields you need, apply filters, and then connect Power BI to that prepared data source.
Why it may help in this scenario:
- Object and field visibility is controlled from Salesforce permissions.
- It supports standard and custom Salesforce objects.
- You can preview selected objects and fields before using them in Power BI.
- SOQL mode is available if you need more precise Salesforce-side logic.
- If you also use Salesforce Reports, it avoids the frustrating Salesforce Reports 2,000-row limit.
- There is a 30-day free trial, so you can test it on the same object before committing.
Docs: https://metricasoftware.com/docs/salesforce/
Support: https://metricasoftware.com/docs/salesforce/contact-support/
Disclosure: I am with Metrica. If helpful, we can also set up a quick demo and walk through object visibility, permission checks, data source creation, and the Power BI connection.
Hope this helps anyone who sees Salesforce objects missing in Power BI even though they exist in Salesforce.
Cheers,
Metrica Team.