we discovered that in BC25, table 1400 "Service Connection" was changed to a tempoary table.

this presents a big problem, as there may have been third party appsource and / or PTEs that appended physical records to this table. in this case we discovered an older version of a third party ISV product was the culprit.

since this table needs to be devoid of ANY physical records across all companies, synchronizing the base app (mode=add) WILL fail when upgrading to the BC25 base app.

currently there is no adequate solution other than writing a PTE to purge that table across ALL companies in <= BC24 before upgrading to BC25.

since this is a harmless delete, I feel this could have been mitigated if the BC platform supported a new codeunit subtype=sync with OnSyncPerDatabase and OnSyncPerCompany triggers (thus allowing the base app to clean up these tables at the sync step BEFORE the schema is synchronized).

this would greatly benefit not only saas but the dev community as a whole.