set offline cache expiration greater than 30 days

Hi Andreas,

Thank you for the request.

It's quite easy to change the upper limit. The question then becomes what should the upper limit be? 60, 90 or 180 days?

So that I better understand the request. Why is 30 days not enough? Do you actually have users that are not able to connect to your data source, via VPN or otherwise, for more than 30 days? Are they read/write offline? What is your use case?

Best regards,

Hi Stéfane,

up to 180 days would be very nice and would be enough in my mind.
We don't have the need for vpn for our users for other cases. The only need would be RDM.
But for that we don't want to buy vpn licenses for all users.
Sometimes we have users who can't connect to our local sql server because they are traveling very much.
Maybe 60 or 90 days would be enough but i think 180 days would cover it all ;-)

Best Regards,
Andreas

Fair enough thank you for the feedback. We've added a change request. The change will be available in the upcoming v2021.1 release.

Best regards,