3727286 - New Model data import uses the Classic UI and import jobs disappear upon model changes in SAP Analytics Cloud (Neo)

• When attempting to import data into a New Model (Measure-Based) in SAP Analytics Cloud, the system loads the "Classic Data Import" interface (the legacy grid/sidebar view) instead of the expected "New Data Import" experience (the flow-based wrangling view).

• The user cannot find the flow-based data preparation tools despite explicitly creating a New Model.

• Additionally, when the structure of the New Model is modified or updated (e.g., adding or removing measures/dimensions), draft import jobs in the Data Management tab disappear and must be recreated from scratch.

• SAP Analytics Cloud 2025.21.11 
• SAP Neo Environment

Issue 1: Classic UI appearing for New Models

1. Log in to an SAP Analytics Cloud tenant hosted on the Neo environment.

2. Go to Modeler and create a New Model (Start with Data).

3. Select a data source (e.g., MS SQL Server via SAP Analytics Cloud Agent or OData).

4. Proceed to the Data Preparation/Wrangling stage.

5. Notice that the system displays the Classic Data Import UI rather than the New Data Import flow-based UI.

Issue 2: Import Jobs disappearing

1. In the New Model, navigate to the Data Management tab.

2. Observe an existing draft import job.

3. Switch to the Model Structure view and make a change (e.g., add a new column or measure).

4. Return to the Data Management tab.

5. Notice that the previously created draft import job is no longer listed.

Both behaviors are Working by Design.

Cause 1 (Interface Fallback):

The root cause is a platform architectural constraint. The "New Data Import" experience (flow-based view) was developed exclusively for Cloud Foundry (CF) environments. On the Neo platform, the system is designed to force the Classic Data Import interface, even when interacting with New Models.

Cause 2 (Disappearing Import Jobs):

The system is designed to strictly enforce data integrity. When a model's structure is updated or changed, the system automatically invalidates and deletes previous draft mappings. This prevents data corruption or upload failures that would occur if the old mapping tried to push data into a structure that no longer exists.

For the Interface Behavior:

• Because this is a hard platform constraint on Neo, there is no system configuration or workaround to enable the New Data Import experience on a Neo tenant.

• To utilize the New Data Import experience and flow-based wrangling, the tenant must be hosted on a Cloud Foundry (CF) environment. Customers wishing to use these features should consider migrating their tenant from Neo to Cloud Foundry.

  • Reference KBA:  3119338 - Migrate SAP Analytics Cloud NEO tenant to Cloud Foundry 

For the Disappearing Import Jobs:

• This is expected behavior. To minimize rework, it is highly recommended to finalize the Model Structure completely before setting up and mapping Data Import jobs.

• KBA  3119338 - Migrate SAP Analytics Cloud NEO tenant to Cloud Foundry
• KBA 2569847 - Where can you find SAC user assistance (help) to use, configure, and operate it more effectively?
• KBA 2487011 - What information do I need to provide when opening a case for SAP Analytics Cloud?
• KBA 2511489 - Troubleshooting performance issues in SAP Analytics Cloud
• SAP Analytics Cloud Connection Guide
• SAP Analytics Cloud Get More Help and SAP Support
• Need More Help? Contact Support 

Your feedback is important to help us improve our knowledge base.

SAP Analytics Cloud, SAC, Neo, Cloud Foundry, CF, New Model, Classic Model, Data Import, Data Management, Data Preparation, Wrangling, flow-based, fallback, missing, UI, interface, disappear, deleted, rebuild model, import job, draft source, Classic UI, MS SQL Server, mapping.  , KBA , LOD-ANA-AQU , Import Data Connections (Acquiring Data) , Problem