<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Copying/recreating a Meta Data source between similar projects]]></title><description><![CDATA[<p dir="auto">Re: <a href="/topic/5946/copying-recreating-a-meta-data-source-from-project-to-project">Copying/recreating a Meta Data source from project to project</a></p>
<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/user/sgaf" aria-label="Profile: SGAF">@<bdi>SGAF</bdi></a> apologies for the long delay on this; here’s a complete walkthrough.</p>
<p dir="auto"><strong>Exporting the Meta Data Source</strong></p>
<ol>
<li>Go directly to the Meta Data Source itself (Data Integration &gt; Data Sources, select it).</li>
<li>Click the ⋮ menu in the top right and choose <strong>Export with points</strong>, this exports the data source and all its meta points together as JSON in one step, without going through the full Import/Export page.</li>
</ol>
<p dir="auto"><strong>Preparing the JSON for the new site</strong></p>
<ol start="3">
<li>In the exported JSON, give the Meta Data Source a new, unique <code>xid</code> for the new site (e.g. <code>META_SITEB</code>), unless you intend to overwrite an identical one already on the target.</li>
<li>For every meta point under <code>dataPoints</code>, update its <code>dataSourceXid</code> to match the new Meta Data Source’s <code>xid</code>, and give each point its own unique xid as well (e.g. prefix with the site name, like <code>SITEB_DP_ZoneTemp</code>).</li>
<li>This is the step you already identified: each meta point’s script references <strong>context points</strong> by XID (the real underlying data points it reads). Those context XIDs need to be remapped to the equivalent real points on the new site before importing.</li>
</ol>
<p dir="auto"><strong>Importing</strong></p>
<ol start="6">
<li>Go to <strong>Administration &gt; Import/Export</strong>, paste or upload the edited JSON, and import. You need an admin account, non-admin users get a “Permission denied” error on import.</li>
</ol>
<p dir="auto"><strong>On the error you hit</strong><br />
The most common causes of an import failing are:</p>
<ul>
<li>A data point’s <code>dataSourceXid</code> doesn’t match any data source in the import or on the target (often from a typo when reassigning XIDs)</li>
<li>A duplicate XID that collides with something unrelated already in the system</li>
<li>Malformed JSON from a manual edit (missing comma/bracket), which shows up as a generic “Bad Request” instead of a specific error</li>
</ul>
<p dir="auto">If you still have the exact error message or result summary Mango gave you, paste it here and we can pinpoint it directly.</p>
<p dir="auto"><strong>One more option:</strong> if you’re doing this for many similar sites, it may be worth scripting the XID remap with something like <code>jq</code> against the exported JSON rather than editing by hand each time, this avoids the typo/bracket issues above. Happy to help put that together if it’d save you time.</p>
]]></description><link>https://forum.mango-os.com/topic/6198/copying-recreating-a-meta-data-source-between-similar-projects</link><generator>RSS for Node</generator><lastBuildDate>Fri, 30 Oct 2026 11:17:55 GMT</lastBuildDate><atom:link href="https://forum.mango-os.com/topic/6198.rss" rel="self" type="application/rss+xml"/><pubDate>Thu, 29 Oct 2026 12:42:26 GMT</pubDate><ttl>60</ttl></channel></rss>