I'm going to go a step further and say the whole "Configuration Sync" needs to be overhauled.
It came from the days when combined networks did not exist. If you had three types of kit such as MR, MX and MS they all had to go into seperate networks (and the Meraki mobile app still maintains this concept).
Using configuration sync from one wifi network to another worked just fine.
Then came long combined networks. Configuration sync was not updated to support these. And you mention there is also an issue with Systems Manager style networks.
Because 99.99% of all networks created now are combined networks - configuration sync is now unusable.
“The reason why you get an error while you try to sync your Corporate to a SSID in a different network is because under that SSID you have enabled Systems Manager Sentry Wi-Fi Security which does not allow the sync. If you disable the this feature and try to sync the SSIDs I believe you should be able to successfully sync the configurations on the network. Let me know if you have any furthur questions.”
This is NOT a proper answer because it simply do not solve our problems.
We shouldn’t have to disable anything for it to work .
Configuration sync is also NOT working properly with other settings, I am wondering what should I disable for it to work.
For memory “other settings” are well copied from a copy of Network and are not able to sync using “configuration sync” with a network created from scratch .
I would be very happy if a PM can answer and help to resolve / review / improve the “configuration sync” functions.