Unanswered

Data Movement Service Request Objects Are Being Added to My Solution

(1) Share

Report

Posted on by EricFai

Hi, I've seen over the past few months there are these "Data Movement Service Request" and "Data Movement Service Request Status" objects being added to my solution. Are these necessary and expected behaviour?

I've been removing them from my solution before deploying from this (Dev) envionrment to our Test environment.

I have other solutions that have over 100-200 of these objects. They all use Dataflows.

On another Note, when I publish a new Dataflow, I see the Dataflow gets duplicated (i.e. a second Dataflow with the same name is created). Any thoughts on this? I may open another question for this issue.

Thank you very much for your help

Eric

Categories:

Power Apps Pro Dev & ISV

I have the same question (0)

All responses (3)

Answers (0)

Suggested answer

stampcoin 5,058 Super User 2025 Season 2 on at

Like (0)

Report

@EricFai Hi,

Those are expected behaviour. Those are used by Dataflows to track and store metadata and execution status for data movement operations I think. it's like a log.

Regarding duplicated data flow, you can query the dataflow table if anything useful information there, each record is unique.

Enjoy Power Platform and have a great day 🚀 | My LinkedIn

If the answer helps, please consider 👍, Thanks.

Was this reply helpful? Yes No
EricFai 44 on at

Like (0)

Report

Thank you very much @stampcoin

In this case, should I be including all of these Data Movement Request objects in the solution when I deploy from my Dev environment into Test and Production?

Re: the duplicate dataflows, I noticed that they are duplicated once I hit publish on the dataflow. The dataflow table does show the duplicate (same name but different ID).

Any additional thoughts wlecomed.

Thank you so much

Eric

Was this reply helpful? Yes No
stampcoin 5,058 Super User 2025 Season 2 on at

Like (0)

Report
@EricFai Hi,

I don't think so, since I cannot reproduce this in my environments. So keep cautious.

When you check those, select the advanced on the top of the view.

Check dependencies, normally it shouldn't have any.

Check solution layers. from there you may see more detail ( Property name, Value).

For the Data movement tables (2) , you can check the dependencies as well.

Regarding the duplications,
I also checked one of my environment.

each of the task ( for example data import), two records. one with RefreshHistory value, one without.

my conclusion is those records are for log/trace purpose.

As I said, be cautious.

Was this reply helpful? Yes No