manifest

To configure a Domo app manifest, you define datasetsMapping, collectionsMapping, workflowMapping, and packagesMapping within your manifest.json file. This ensures correct resource wiring by mapping aliases to actual resource IDs for datasets, collections, workflows, and Code Engine functions.

A manifest.json file centralizes app metadata and resource mappings for Domo app publishing. It documents required assets and connects external datasets, collections, workflows, and Code Engine packages to enable automated app deployment across environments.

You map aliases to actual resource IDs in a Domo app manifest by configuring the mapping structures within manifest.json. Each mapping type requires proper dataSetId and field structures to correctly wire datasets, collections, and workflows to your app.

Publishing a Domo app with a manifest requires a manifest.json file defining your app metadata and mappings, along with a 300x300 thumbnail.png in the same directory. These assets ensure the app is correctly packaged and displayed during the create and update lifecycle.

Yes, you can use Domo Code Engine functions with manifest mapping by defining a packagesMapping structure in your manifest.json. This connects your Code Engine packages to the app, ensuring proper resource wiring alongside datasets, collections, and workflows.

If Domo app datasets are not connecting, your manifest.json likely has incorrect or missing datasetsMapping structures. You must ensure proper dataSetId values and field structures are defined so the manifest correctly wires aliases to the actual dataset resource IDs.