When I create a relationship between two tables and it states it will delete an attribute (like in the picture) does that mean metrics etc can't refer to it?

Yes — based on your screenshot, the LDM modeler is showing that creating the relationship with "App adjusted parts data" will delete the attribute "Quoted Part No", and 53 objects will be affected (the ⚠️ 53 warning). When an attribute is deleted, the impact is significant: • Metrics that use it are no longer listed in Metrics or Analytical Designer (they become inaccessible via the UI, though they may still exist as "phantom" objects in the backend). [Monitor Model Changes] • Visualizations that use it are no longer listed in Analytical Designer. [Monitor Model Changes] • Dashboards will show an error: "Sorry, we can't display this insight" in place of affected visualizations. [Monitor Model Changes] • Any dashboard filter based on that attribute is automatically deleted. [Monitor Model Changes] Importantly, the affected objects are not automatically remapped to the new relationship/dataset — you would need to manually update them. [Community Slack] Recommended safer approach Instead of letting the modeler delete the attribute, consider: 1. Create the new dataset (e.g., "App adjusted parts data"). 2. Move the "Quoted Part No" attribute to the new dataset and make it the primary key there. 3. Create a reference from the new dataset back to the original table. Moving an attribute (rather than deleting it) preserves its identifier, so existing metrics, visualizations, and dashboards should remain intact. [Community Slack] You can click Open list (the ⚠️ 53 warning) to review exactly which objects will be affected before saving. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups. 👀 Our Support team monitors all messages and will jump in if needed.