Unanswered

Data Migration - prod to dev

(0) Share

Report

Posted on by Ryan01

I am loading data from prod environment to a dev environment using dataflows and odata connector. I have the schemas all defined in Dev and I have completed most of the table transfers already but a couple will not load.

Example: Table 1 move from prod to Dev.

Dataflow fails with message: Failed due to customer installed plugin. "column 1 can not be null"

this "column1" is a lookup column in this Table1, but it lookups itself (The relationship it has is with itself).

Now my question is: I have to load this column before the Table1 otherwise it can't "lookup" so I'm wondering what's the best way to deal with this in power apps? How do i load the parent column before the table if it's inside the table. Do I have to split it ?

Categories:

Microsoft Dataverse with Power Apps

I have the same question (0)

All responses (3)

Answers (0)

Sort by

Michael E. Gernaey 53,978 Moderator on at

Like (0)

Report
Copy link

Link copied!

@Ryan01

Try disabling the plugins, then load the data, then reenable the plugin

If you like my answer, I would really appreciate if you please Mark it as Resolved, and give it a thumbs up, so it can help others

Cheers

Thank You
Michael Gernaey MCT | MCSE | MCP | Self-Contractor| Ex-Microsoft
https://gernaeysoftware.com
LinkedIn: https://www.linkedin.com/in/michaelgernaey

Was this reply helpful? Yes No
Ryan01 4 on at

Like (0)

Report
Copy link

Link copied!

Hi Michael,

Didn't work. I am migrating a table from prod to dev and there are 2 columns in this table that are lookups. The table that they lookup is itself so they are self lookups. These lookups are parent categories so they must be loaded first somehow. Creating a mapping table of some sort with the GUIDS will work but is there no easy way of migrating lookups ?

Was this reply helpful? Yes No
Michael E. Gernaey 53,978 Moderator on at

Like (0)

Report
Copy link

Link copied!

@Ryan01

Are the lookups multi-level?
So Record A is the first record
Record B looks up A
Record C looks up B
etc?

Also how many rows are we talking (this can change what I suggest)

Depending on the total situation you have
1. Use Dataflows to migrate them (not sure how you are now)
2. Export the data but when you do, sort them by either Date Created, or Date Modified again it truly depends on some details.
3. If its not multi-level, then that means all the "Parents" would have no parent, only children, which mean you should sort by where the lookup is NULL and insert those first

You could backup Prod, and restore it IN the dev environment and you dont have to worry about data import, it will all just be there.

If you like my answer, I would really appreciate if you please Mark it as Resolved, and give it a thumbs up, so it can help others

Cheers

Thank You
Michael Gernaey MCT | MCSE | MCP | Self-Contractor| Ex-Microsoft
https://gernaeysoftware.com
LinkedIn: https://www.linkedin.com/in/michaelgernaey

Was this reply helpful? Yes No