Resolve primary keys, manual relations and blockers, start the import, check failed rows and deploy.
Welcome back. Let's finish the journal import, start it, and take the journal live.
Here's the draft we left. Remove would delete it, so click Continue. Everything is just as you left it. Hide the sidebar again, to make room.
First, that red alert. The seasons table has no primary key in the dump. Pick one yourself: the id column. If a table has no id at all, let SearchAPI generate one instead.
Primary keys aren't the only thing a dump can miss. Some don't declare every foreign key either. Each author has a home topic, but the dump doesn't link it. Click the plus icon next to its type, and pick topics. Now it's a relation too, and you can rename it: home topic. Above the fields, Depends on lists the tables this one links to.
Links also decide what you can remove. A table that others link to can't be removed. Authors are embedded in articles, so Yes, Remove It! stays off. Click Close. Model names are unique across your company. Type one that's taken, and you can't start until you change it.
Those were the blockers. Next, a quick look at a few optional settings. On the pivot, Pivot connecting shows which column points to which table. On topics, SearchAPI picked parent id as the self-reference. If you don't want a tree here, click it again to turn it off. But if you want it back, click once more. Back in articles, Required and Searchable work just like on any model. Make the title and summary searchable.
That's every setting. Time to import: click Start import. Each table runs as its own job, and the pivot is resolved into the articles. One article failed. Under the articles, click View this table's import job. Its failed rows are listed there, just like any import. Here, the featured value is two, which isn't a boolean. To fix it, correct the value, and add the article again: one by one in Data UI, or with a CSV import into the articles model.
The other twenty-four articles were imported. Click the menu icon, and open Data UI. Choose the Journal API, its version, and the articles model. Each article holds its author, its topic with the whole tree above it, and its seasons.
Last, this version isn't live yet. Open APIs, and click Api Version List. A version needs an API key on its endpoints before it can deploy. Click Set API Keys. The journal gets its own key: click Create API Key, name it journal, and click Create. Turn on Apply to all endpoints, and save. Now click Deploy. Your journal is live. In the next guide, we'll take a closer look at Data UI.
Read the details behind this guide on the documentation page.