When working with Data Entities from Dynamics 365 Finance and Operations (D365 F&O) using OData in Power BI and encountering issues with the cross-company=true parameter, it's important to troubleshoot a few key areas to resolve the issue. Here are steps and considerations to help address the "400 Bad Request" error:
- Check OData URL Syntax
Ensure that your OData URL is correctly formatted. The cross-company=true parameter should be added to the query string. For example:
https://<your-dynamics-instance>/data/<EntityName>?cross-company=true
Verify that there are no typos or incorrect characters in the URL.
- Validate Entity Access and Permissions
Ensure that the entity you are trying to access is properly set up for cross-company queries. You may need to verify that the user account used for the OData connection has the necessary permissions to access data across companies.
- Verify Entity Configuration
In D365 F&O, check the configuration of the data entity. Ensure that:
- The data entity is published.
- The entity is marked as "Cross-company" in its configuration if required.
- Test URL Directly
Try accessing the OData URL directly from a web browser or a tool like Postman with the cross-company=true parameter to see if you receive a more detailed error message or if the request succeeds. This can help isolate whether the issue is with Power BI or with the OData service itself.
- Update Power Query M Code
Ensure that your Power Query M code correctly handles the request. For example:
let
Source = OData.Feed("https://<your-dynamics-instance>/data/<EntityName>?cross-company=true", null, [Implementation="2.0"])
in
Source
Make sure the URL is correctly substituted with your actual instance and entity name.
- Check OData Version
Confirm that you are using the correct OData version for your Dynamics 365 instance. D365 F&O typically uses OData V4, but there may be specific configurations or requirements for different versions.
- Review Dynamics 365 Documentation and Updates
Review the official Dynamics 365 documentation to see if there have been any changes or updates regarding the use of OData with the cross-company parameter.
- Check for Known Issues or Updates
Sometimes issues are due to known bugs or limitations in the platform. Check Microsoft's support forums or service status updates for any known issues related to OData in D365 F&O.
- Contact Support
If the problem persists after trying these steps, consider reaching out to Microsoft Support for more detailed troubleshooting. Provide them with the error message, URL, and any relevant details about your environment.
By following these steps, you should be able to diagnose and resolve the issue with the cross-company=true parameter in your OData requests from Dynamics 365 F&O to Power BI.
