web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

Community site session details

Community site session details

Session Id :
Finance | Project Operations, Human Resources, ...
Unanswered

D365 Finance & Operations, with update 48 data import always send data to target

(0) ShareShare
ReportReport
Posted on by 30

Hi everyone,

I'm currently on a data migration project and my approach has always been to import data de-selecting "skip staging" option (as I upload the file creating the entity) and then de-selecting "execute target step" for the execution process (choosing re-import).

This allowed me to set the data on the staging table for a check and possible manipulation before sending to target, but as update 48 came in, the process always send data to target ignoring the settings of the 2 options mentioned above (skip staging do not appear anymore as I upload the file but i de-select it after adding the column on the entity line and on the execution process).

Can anyone tell me if it is a possible bug or if there is a specific setting to let me place the data on the staging without starting the execution on target ?

thanks in advance

Data_5F00_import_5F00_update48.pptx

I have the same question (0)
  • André Arnaud de Calavon Profile Picture
    301,035 Super User 2025 Season 2 on at

    Hi Alegigante,

    For importing data there is no option to skip the staging. It will always use the staging. I only have a machine running with update 49, so can't check your issue. In this environment the Skip staging field is not visible for import projects.

    I would imagine that indeed when using re-import and not executing the target, then it should not perform that action and only have the data imported in the staging table.

    Have you checked LCS issue search for a possible known issue? If you can't find it, you can contact Microsoft Support by creating a new ticket.

  • alegigante Profile Picture
    30 on at

    Thanks for your reply,

    we found out that it is possible to set a flight as workaround to let the correct behaviour:

    INSERT INTO SYSFLIGHTING
    ([FLIGHTNAME]
    ,[ENABLED]
    ,[FLIGHTSERVICEID]
    ,[PARTITION]
    ,[RECID]
    ,[RECVERSION]
    )
    VALUES ('DMFDisableBatchReImport', 1, 12719367, xxx, xxx, 1)

    where xxx is the partition id

    best regards

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Leaderboard > Finance | Project Operations, Human Resources, AX, GP, SL

#1
Martin Dráb Profile Picture

Martin Dráb 565 Most Valuable Professional

#2
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 450 Super User 2025 Season 2

#3
Sohaib Cheema Profile Picture

Sohaib Cheema 250 User Group Leader

Last 30 days Overall leaderboard

Product updates

Dynamics 365 release plans