This is a bit old topic, but I have encountered the same issue. This seems to be a bug with Power Pages, which Microsoft would need to resolve. However, I couldn't find any way to report this, so I am hoping that someone from Microsoft is reading this topic and forwards this issue to the developer team 🙂
TL;DR - The Power Pages editor uses the Relationship table name instead of the Relationship name (incorrectly) for N:N relationships, causing the following exception in the portal: Retrieve relationship request failed for relationship name ******* was found at controller: EntityGrid and action: GetSubgridData, Category:Exception, ErrorCategory:ApplicationError". Creating / updating the Table Permission in the Portal Management app resolves the issue, as it uses the correct name.
To resolve the issue, follow these steps:
- Make a note, that in the Power Pages editor, when you open the table permission, you see the Relationship table name in the relationship field (in your case it is cr2c5_account_contact).
- In Power Pages, choose the Portal Management option in the navigation menu (can be found under the three dots in the left menu).
- Choose Table Permissions in the sitemap and find the table permission you have created by its name.
- Note that the Dropdown field in the Contact Access Type section is empty.
- Open the dropdown and select the correct relationship. Note that when you make the selection, it will show the relationship name instead of the table name (in your case it is cr2c5_Account_Contact with a capital A & C).
- Save the changes, go back to Power Pages and Sync the changes to flush the cache of the website.
Please let me know if this fixed the issue for you as well, but I hope you have been able to find a workaround for the issue since then.