Share
Report
60Good Morning everyone.
I'm facing very strange behavior related to portal URL handling. I'm almost sure it used to work correctly but now it doesn't.
When I want to share a portal link that leads straight to a case record like so:
<my-site-name>.powerappsportals.com/support/edit-case/?id=673937f7-075f-eb11-a81c-000d3abe331f
When the person that receives this link is already logged in and has the right to access that record it works as expected.
The problem becomes apparent when a person is not logged in and after clicking a link, Portal redirects that user to the login page, updating the URL to:
<my-site-name>.powerappsportals.com/SignIn?ReturnUrl=/support/edit-case/&id=673937f7-075f-eb11-a81c-000d3abe331f
That part after ReturnUrl is what tells the portal where to go after successful login, but it is wrongly constructed as it should be a question mark (?) instead of the ampersand (&) colored red in the URL above.
So when I logged in, the request goes straight to <my-site-name>.powerappsportals.com/support/edit-case/ leaving out the id of my record (the part that begins with an ampersand).
When I manually update ampersand to question mark and hit enter and then log in, it takes me to my record, otherwise, it obviously tells me that the record was not found as the id was cut out of the URL.
Please someone could help me out with this problem? Could you confirm that this behavior is present on your portals?
Thanks,
Konrad
All responses (
Answers (
