I'm currently struggling to get our Salesforce into a version control system with the "source" metadata format. And, of course, I want this repo to be deployable.
After about 16 ours of hacking away, I've finally figured out a subset of metadata which might be considered an essential "core".
This includes Zip_Code_Area__c, which has its own custom Lightning Record Page, which we also need.
However, deploying each of this Page is proving problematic.
Zip_code_Area_Record_Page.flexipage-meta.xml fails with "In Lightning component sortablegrid:sdg, property SDGConfiguration has an invalid value CustomObject:ZipCode Area Craftsman."
I can't seem to find any information how to fix this, but maybe (for now) we might be able to ignore it.
While I might be able to fix these issues by manually removing these references from the flexipage metadata, it would be a terrible workflow if we need to manually do this every time before we push the metadata and there would be the risk of accidentally commiting these changes. And obviously we don't want to commit these changes because eventually this repo should be part of the pipeline and we don't want to remove these things from production.
Any ideas how we should deal with this?