Hi @Roberto_corella ,
a colleague of mine always says, in software you face two hard problems: naming of variables and caching 🙂
To overcome caching of the data, i sometimes do a fetch for the data in the page itself with a where statement like createdon < current date (https://docs.microsoft.com/en-us/power-apps/maker/portals/liquid/template-tags#fetchxml ). As the current date usually changes when loading the page, a request is made to the dataverse getting new data. This then usually reflects the new data on the page.
For example:
{%- fetchxml bypasscache -%}
<fetch version="1.0" output-format="xml-platform" mapping="logical" no-lock="true">
<entity name="account" >
<filter>
<condition attribute="accountid" operator="eq" value="<the loaded accountid from request.params["id"] for example" />
<condition attribute="createdon" operator="le" value="{{ now | date: 'yyyy-MM-ddTHH:mm:ss'}}" />
</filter>
</entity>
Of course, you have to read something from that fetch. If you like to refresh dependent data, you might wnat to fetch for example contacts whith condition parentcustomerid = myid or something like that.
Give it a try, whether it resolves your cache issues.
Hope it helps and does not sound too creepie,
Christian
</fetch>
{%- endfetchxml -%}
But do this only when the data is to be refreshed. It increases the number off calls to the dataverse and with high tghraffic you could get in touch with throttling https://docs.microsoft.com/en-us/power-platform/admin/api-request-limits-allocations
