Most problems when building a data product come from a rule doing its job. Dawiso blocks a product from advancing when it would be incomplete or would break another team’s product, and the block is usually the fastest explanation of what is missing.
| Symptom | Likely cause | Fix |
|---|---|---|
| Cannot move the product out of draft | It has no output port | Add an output port |
| Cannot publish — a port is flagged as empty | An output port has no assets attached | Attach at least one asset to every output port |
| Cannot publish — an input port is flagged | An input port has no upstream source | Wire it to an upstream output port, or remove it |
| An asset is missing from the picker | Another product already publishes it | Consume the upstream port instead |
| An asset cannot be added to a port | Its technology differs from the port’s | Put it on a separate port |
| A contract cannot be attached | The port already has one | Reuse or replace the existing contract |
| The product is not in the Data Market | It is not in production, or visibility is too narrow | Publish it, then check visibility |
| The domain is missing in the wizard | The Space has no Data Product Standard application | Add the application to the Space |
The product cannot leave draft
Cause. The product has no output port. A product with nothing to deliver has nothing to build toward, so this rule is enforced.
Fix. Open the Ports step or tab and add an output port, then attach the assets it publishes. See Working with ports.
Publishing is blocked by an empty port
Cause. An output port exists but carries no data assets. An empty port would appear in the Data Market as a delivery promise with nothing behind it.
Fix. Attach at least one asset to every output port. If a port is a placeholder you no longer need, delete it instead of leaving it empty.
Publishing is blocked by an unwired input port
Cause. An input port has no upstream source. Input ports record where your product reads from, so an unwired one is an unfinished dependency.
Fix. Wire the input port to the upstream product’s output port, or delete it if the dependency no longer exists. A product with no input ports at all passes this check.
An asset is missing from the picker
Cause. The asset is already published through another product’s output port. A product cannot re-expose another product’s output, so the asset is not offered to you.
Fix. Consume it instead of republishing it. Add an input port pointing at the upstream output port, which records the dependency and keeps the upstream owner accountable for their data. If you believe the asset is in the wrong product, talk to that product’s Owner rather than working around it — see Data product anti-patterns.
An asset cannot be added to a port
Cause. The port’s technology is set by the first asset attached to it, and every other asset must match. A BigQuery port cannot also carry a Power BI report.
Fix. Create a second output port for the other technology. This is deliberate: one technology per port keeps each port’s delivery format, contract, and access model consistent for consumers.
A contract cannot be attached to a port
Cause. Each output port can be covered by only one data contract.
Fix. Remove the existing contract from the port before attaching a different one, or reuse the contract that is already there. One contract can cover several ports that share the same guarantees. See Data contracts.
The product does not appear in the Data Market
Cause. Either the product has not reached production, or its visibility restricts who can see it.
Fix. Check the workflow state first — Save For Later parks a product in announcement, which is not published. If the state is correct, check the visibility setting on the Basics step. See The data product lifecycle.
The domain does not appear in the wizard
Cause. The Space you selected has no Data Product Standard application, or the domain has not been created yet.
Fix. Add the application to the Space, then create the domain. The wizard only lists Spaces that have the application, and only domains that already exist — it does not create either for you.
Wizard progress seems lost
Cause. You left the wizard before finishing.
Fix. Reopen it. The wizard autosaves your progress and offers to resume the draft or start over. Choose Resume draft to continue where you stopped.
Prevent most of these
The blocks above cluster at two moments: leaving draft and publishing. Both are checkable in advance — running through the Pre-publish checklist before you start the review step catches the enforced rules while they are still cheap to fix.
If a block does not match anything here, the product’s Completeness panel on the review step lists what is missing, and each item links back to the step that owns it.