Exporting solution does not include records that are used by views to filter on...

(0) Share

Report

Posted on by KoJaPD

601

Dear all,

(sorry, the title is a bit hazy)

I have created quite some predefined views on some entities, using lookup fields to filter those views.

However, when I export/import these views through a solution, the records used in those lookup views are not in the solution. This means the filters on those predefined views are not working. Even when I recreate the lookup records in the new environment, the filters have lost their connection with the predefined lookup values; So I have to go through every view in the new environment and re-apply the filters to use the (newly) added lookup records...

This is how it looks after importing the solution:

This is how it should look (after re-applying the filter):

How can I export those records in the solution so the predefined filters keep working when importing the solution in another solution?

Thanks,

Koen

Categories:

Power Apps Pro Dev & ISV

I have the same question (0)

All responses (4)

Answers (1)

Sort by

Verified answer

Mira Ghaly 11,415 Moderator on at

Like (1)

Report
Copy link

Link copied!

@KoenJanssensPD

You can use a tool like Data Transporter in XRMToolbox

https://www.xrmtoolbox.com/plugins/Colso.Xrm.DataTransporter/

To Transfer records using the same GUID across environments.

Was this reply helpful? Yes No
KoJaPD 601 on at

Like (0)

Report
Copy link

Link copied!

This is indeed one way to transfer records between environments...
But what if I don't have access to the (customers') environment and they want to import my solution? They would still miss the lookup records on which the predefined views rely on... Is there any way to include records in a solution?

Thanks,
Koen

Was this reply helpful? Yes No
cchannon 4,702 Moderator on at

Like (0)

Report
Copy link

Link copied!

It isn't the most fun option, but Microsoft also has a Solution Package Deployer that was originally designed for USD migrations where very large segments of the config are actually data (and guids matter).

Solution Packages allow you to bundle solution zips up with data zips and import them in a single, scripted process that you can design. This would allow your customer to run the import process when you don't have access (you can even set up a GUI "click next" kind of import experience) but it takes quite a bit of knowledge and work to set it up and you'll find pretty quickly that updates will be needed frequently as your solution evolves.

Was this reply helpful? Yes No
a33ik 3,306 Most Valuable Professional on at

Like (0)

Report
Copy link

Link copied!

Hello,
You can use Configuration Migration Tool to move that data - https://docs.microsoft.com/en-us/power-platform/admin/manage-configuration-data

Was this reply helpful? Yes No