This is a known issue in Sitefinity 7.0 and there is not a workaround available for this version. Fortunately, the issue is fixed in Sitefinity 7.1. So, what I can suggest is to perform an upgrade to the latest Sitefinity version in order to resolve this issue. Here is the link
to our upgrade documentation for more details about the upgrade procedure.
Do you want to have your say in the Sitefinity development roadmap? Do you want to know when a feature you requested is added or when a bug fixed? Explore the Telerik Sitefinity CMS Ideas&Feedback Portal
and vote to affect the priority of the items