For the most part I don’t blog about the (roughly) monthly releases for Power Apps Portals, mostly because they deal with bug fixes for relatively obscure issues. However, last month I was happy to see a few items on the list that I’ve been waiting for, and I thought were worth sharing.
Full release notes can be found here.
In December I blogged about the chances to caching in Power Apps Portals. While I was playing around with the new Clear config button, it didn’t work at all as I expected. It turned out that is actually worked most of the time, just not for the one attribute I was testing with: adx_copy on the Web Page entity.
As discussed is my previous blog post, certain entities are now cached indefinitely – this includes the Web Page entity. However, by going to https://yourportal.powerappsportals.com/_services/about as an administrator, clicking the Clear config button should refresh any changes for those entities that are cached indefinitely. Now that the bug has been fixed for the adx_copy attribute on the Web Page, this should work for all of those entities.
You always could have used the Clear cache button, but there was a greater performance hit with clearing the entire cache, as opposed to clearing just the “configuration” entities.
Rewrite Page Templates are a bit of a blast-from-the-past – they are left-over from the Adxstudio days where we all had access to the website code. Since we no longer can add our own new Page Templates of this type, when an issue was introduced that caused Entity Lists and Entity Forms to not be displayed when choosing one of the Page Template types, you wouldn’t think it would be that big of a deal. But for anyone using the geolocation or calendar functionality built into Entity Lists and Entity Forms, it was bad news.
As MVP Nick Doelman pointed out in his blog post, the only way to leverage the maps and calendar functionality was by using Rewrite Page Templates. When those templates stopped showing Entity Lists and Entity Forms, there was no way to display the maps or the calendar.
More than a couple people asked about this on the community forums over the past few weeks, so I’m happy to see that this issue has been resolved.
I’ll be the first to admit I don’t know all the details about what this one means, but it’s not the first I’ve heard of it, so I thought it would be good to at least spread the word.
At the beginning of February Google is scheduled to release Chrome 80, which includes an update to the way that cookies are handled. Specifically, whereas before the default for the SameSite label for a cookie was None if it wasn’t explicitly defined, going forward it will be Lax. Without getting too much into the details, this means that cookies will only be set when the domain of the cookie matches the domain in the URL of the browser (for more details, see this article). Microsoft and Mozilla are also expected to follow this move.
The good news is that Power Apps Portals has been updated to ensure support with this change. However, there are certain areas outside of the controls of the Portals team that may impact your portal – specifically, external authentication providers.
[…] post Power Apps Portals: Version 9.1.11.x Release appeared first on Engineered […]
Regarding caching, I have an applications/approvals process where applications are made on the portal and assessed both on the portal and on a CDS model app. There is a requirement to show the last five accessed applications on the assessors’ home page on the portal. At the moment, I am calling an http-flow (Power Automate) which uses the CDS, to register the fact that an application has been viewed by a portal user, and then rendering that list on the home page, using fetchxml in a liquid template. Due to caching however, this list is almost always out of date, when it is needed. I have seen this post by your fellow MVP Colin Vermander https://colinvermander.com/2019/08/06/powerapps-portals-api-clear-cache/, but that seems to me like taking a sledge-hammer to a mosquito.
Is there a better way to achieve this? One that means I always get the correct list every time? If there was selective cache invalidation at the entity level, as opposed to configuration/non-configuration level, then maybe, but in its absence, is there anything else one can do?
Unfortunately nothing else that I’m aware of. There has been talk about an API that would allow you to invalidate the cache more precisely, but no timelines for that functionality that I’m aware of.
I agree, Colin’s approach is interesting, but is not supported by Microsoft so I would recommend it in a production environment.
Thanks for sharing this helpful & wonderful post. I really appreciate your hard work. this is very useful & informative for me.Refer this link for Power Apps portal.
microsoft dynamics crm portals
we are using adxstudio portal latest version with dynamics 365 9.1 and we now struck where the html web resource which load the entity list, attributes and forms and subgrids lists on the web from step, meta data entities is not working.
can we have latest js and html resources in power portal and be used same in old adxstusio version ?
Hmm, good question. I’ve never tried it myself, but I don’t think a lot has changed with those areas, so there is a chance it might work.