[Closed] Product data can't be copied when setting acf-field-group is non translatebale

When choosing to copy product content from original language to secondary language, fields such as attributes and variations aren't discovered by WPML and therefore can't be copied.
This happens when the setting acf-field-group is set to Non translateable.
When it is set to Translateable, these fields get copied from the original language which is preferred.

The problem is that in some cases, as when copying and translating a product, I need the setting to be Translateable, but when it comes to page settings and options page settings, some fields aren't discovered at all, which I need them to be so that their content can be translated or added in secondary language version. For example, I have an options page that consists of a field group for contact information and on pages a field for a panorama image. These are not discovered if acf-field-group is set to Translateable.

I have been searching in your documentation and in forums, but cannot find a way where this global setting doesn't lead to a conflict between the product fields and ACF fields on options pages and pages.

Is there a way to set the global settings to achieve a case where we can both copy all fields from the product's original language and at the same time have all fields on pages/option pages visible for adding/translating content?

Let me know what information you need to investigate this further.
I'd be happy to share a ftp login with you.