Ignore Missing Relations mapping flag
G
Glenn Moen
When you define a relation mapping, entity ingestion will fail when the relation doesn't exist. There is a "createMissingRelatedEntities" flag that when set to true will create dummy entities so ingestion can succeed but you don't always want these dummy entities. There should be a flag like "ignoreMissingRelations" that when set to true would first try to map the relations but would still ingest the entity even if the relation doesn't exist.
S
Simon Beaulieu
Glenn Moen as a workaround that is exactly what "splitting" kind blocks is for. Unfortunately it seems it's been removed from the docs but here's a reference to it from the past: https://github.com/port-labs/port-docs/blob/064243cbad951b66512ce381ad643f732407c2fc/docs/build-your-software-catalog/customize-integrations/configure-mapping.md
G
Glenn Moen
Simon Beaulieu Thanks for the link and the workaround. We have used splitting before, but run into performance issues with long run times going through the kind a second time. My question before posting was: Is it "bad" to have a relationship key that doesn't currently exist? I decided it's similar to a non enforced foreign key in a database table and I am ok with that situation so I 'm ok with this one too.