Frappe CRM build fails because DataImport is not exported?

After a Frappe update, CRM's asset build stops with MISSING_EXPORT. Its import references DataImport, but the expected framework module does not provide that export. New frontend assets may therefore be missing even though other update stages have already run.

A specific app and framework combination

The original report concerns CRM 1.88.0 with Frappe 16.53.0 and describes a changed DataImport component interface. Q1 Official CRM 1.89.0 release notes subsequently list rebuilding the import page around new framework components and a compatibility correction for Frappe 15. Q2

These findings make a compatible version combination the first thing to investigate. They do not guarantee that a single upgrade fixes every installation with custom applications or extensions. Renaming an import alone may also fail to implement the changed component interface correctly.

Make the build failure reproducible

1. Preserve the first relevant error. Record module path, missing export and importing file. Later build errors may simply follow from that initial failure.
2. Create a version matrix. List Frappe, CRM, ERPNext, other apps and Git revisions, together with Node and package-manager versions. Compare the matrix with the last successful build.
3. Identify local differences. Check changes to application source, lockfiles and installed dependencies. Preserve them. Mixing older dependencies with newer source makes a useful comparison harder.
4. Test matching releases on a copy. Produce a clean, isolated build with traceable source and lockfile state. Read the official CRM notes for the framework branch in use. Do not merely copy a filename change from someone else's workaround.
5. Validate the import interface specifically. After the build succeeds, open the import page in the test environment, select a neutral sample file and exercise preview or validation. A completed bundle does not prove the data-import interface works.

Treat deployment as a coherent state

Application source, generated assets and required migrations need to belong together. Before switching traffic, establish how a consistent state would be recovered if the update fails. An improvised framework downgrade or edits to generated bundles can introduce further compatibility and maintenance problems.

Record both the successful build and the narrow browser check with the exact versions tested. This provides evidence for the deployment decision without using a production data import as an experiment.

Frequently asked questions

Can I simply replace the imported name?

Not without checking the new component interface. Parameters, child components or behaviour may also differ. Prefer the maintained application implementation.

What information helps with support?

Provide the first build error, version matrix, relevant local changes and a minimal build sequence. A neutral test dataset is sufficient to inspect the import interface; real customer data is unnecessary.

Help with this case

We can help isolate the affected process and prepare a controlled next step. Discuss case A0542 with KAN KAI WORKS.