'%3e%3cpath%20d='M8%200C12.4183%200%2016%203.58172%2016%208C16%2012.4183%2012.4183%2016%208%2016C3.58172%2016%200%2012.4183%200%208C0%203.58172%203.58172%200%208%200ZM11.6162%204.38379C11.2257%203.99337%2010.5927%203.99338%2010.2021%204.38379L8%206.58594L5.79785%204.38379C5.40732%203.99334%204.77429%203.99329%204.38379%204.38379C3.99331%204.77429%203.99335%205.40733%204.38379%205.79785L6.58594%208L4.38379%2010.2021C3.99348%2010.5927%203.99341%2011.2257%204.38379%2011.6162C4.77426%2012.0066%205.40734%2012.0065%205.79785%2011.6162L8%209.41406L10.2021%2011.6162C10.5927%2012.0066%2011.2257%2012.0067%2011.6162%2011.6162C12.0067%2011.2257%2012.0066%2010.5927%2011.6162%2010.2021L9.41406%208L11.6162%205.79785C12.0066%205.40735%2012.0066%204.77429%2011.6162%204.38379Z'%20fill='%23080E17'%20fill-opacity='0.46'/%3e%3c/g%3e%3cdefs%3e%3cclipPath%20id='clip0_3761_713'%3e%3crect%20width='16'%20height='16'%20fill='white'/%3e%3c/clipPath%3e%3c/defs%3e%3c/svg%3e)
How to Fix a Model-Driven App Record ID URL Issue in Power BI
Question details
The user needs to resolve an issue where creating dynamic URLs for Dynamics 365 model-driven app records in Power BI fails to open the requested record.
- Product
- Power BI
- Device & OS
- not provided
- Scenario
- Appending a record ID to a Dynamics 365 app URL within Power BI to create dynamic navigation links.
- Observed behavior
- Clicking the dynamic URL either prevents navigation entirely or opens the model-driven app without displaying the specifically requested record.
Ensure you have the correct administrative or user access rights in both Power BI and Dynamics 365 before modifying URL structures.
Verify URL Format and Entity Parameters
Check the structure of your URL, specifically focusing on the entity logical name and the record GUID syntax.
A common reason for model-driven app URLs failing to route properly is a malformed URL string. Dynamics 365 requires exact parameter names and correct GUID formatting to successfully load a specific record.
Ensure the URL follows the standard Dynamics 365 format containing the app ID, page type, entity name, and record ID parameters.
Confirm that the 'etn' parameter matches the exact logical name of the entity (usually lowercase), not the display name.
Ensure the appended record ID (GUID) passed from Power BI is correct, formatted without invalid characters, and perfectly matches the target record in Dynamics 365.
Check Access Permissions
Ensure the user attempting to open the link has the necessary permissions in Dynamics 365.
Seek Community Support for Advanced Troubleshooting
Consult official Microsoft communities for complex or persisting environment-specific routing issues.
Need a Lightweight Office Suite for Data Reporting?
While WPS Office does not directly resolve Power BI or Dynamics 365 URL routing issues, it serves as a powerful, free, and lightweight alternative to Microsoft Office for creating, analyzing, and sharing data reports. Enjoy seamless format compatibility and a familiar interface without the heavy subscription costs.
Frequently Asked Questions
Why does my Dynamics 365 URL open the app but not the specific record?
This usually happens if the 'etn' (entity name) parameter is incorrect, the 'id' (GUID) is invalid or improperly concatenated, or the user lacks permission to view that specific record.
How do I dynamically pass a record ID from Power BI to a URL?
You can use DAX to concatenate the base Dynamics 365 URL string with the specific record ID data field, creating a dynamic Web URL column in your Power BI dataset.
What are the required URL parameters for opening a model-driven app record?
The standard parameters required to successfully route to a specific record are 'pagetype=entityrecord', 'etn=[entity_logical_name]', and 'id=[record_guid]'.
