Exporting a theme using the Configuration Migration Tool

[cjbarnaby]

Hi there, 

According to this document , theme "data is stored in the theme table that can be exported and reimported in another environment."  According to this document, the way to do this is to use "the Configuration Migration tool to generate a schema, export the theme data, and import it into a different organization."

When I attempt to create a schema for exporting the data using the Configuration Migration Tool, I can't locate the 'Theme' entity in the Configuration Migration Tool (v 4.0.0.80). The tool only allows selection of entities after first selecting a solution, however since themes aren't solution aware, I'm not sure what 'solution' to select to reveal the 'Theme' entity (I've checked various solutions, including the Default solution, but can't find it anywhere). 

I'd appreciate any assistance with:

• Using the Configuration Migration Tool to create a schema and export data for Theme records; or
• Some other means of exporting a Theme record for import during installation of a solution within a package (eg AppSource and Dynamics CRM Package Deployer).

Thanks.

[Prakash4691]

@cjbarnaby ,

Try OOB export and import.

Adding link for your reference.

https://powerobjects.com/tips-and-tricks/how-to-export-a-theme-from-one-dynamics-365-org-to-another/

If it answers your question, kindly give kudo and accept it as solution.

Regards,

Prakash

[cjbarnaby]

Hi @Prakash4691 , 

Thanks for the suggestion - unfortunately, we need to be able to include the data for import along with several solutions in a Dynamics CRM Package prepared for deployment using the Package Deployer tool (and/or installation via AppSource). According to the MSFT docs I referenced in my original post, it should be possible to export the data using the Configuration Migration tool (and, therefore, included in a crmmigdataimportfile in the package for deployment).

[Prakash4691]

@cjbarnaby ,

If it is data and solution to import at once then it should be package deployer.

Regards,

Prakash

[cjbarnaby]

Yes, I agree. And the docs do suggest that's the idea, I just can't find the Theme scheme in the Configuration Migration Tool, so I can't export the data.

[rampprakash]

Hello @cjbarnaby 

I think it's not possible to migrate using configuration migration tool.

Please mark as Answer if it is helpful and provide Kudos

Subscribe : https://www.youtube.com/channel/UCnGNN3hdlKBOr6PXotskNLA
Blog : https://microsoftcrmtechie.blogspot.com

[cjbarnaby]

For others' benefit, we logged a ticket with MSFT support re: this and they have advised that 'Themes' data cannot be exported/imported using the Configuration Migration Tool (ie, the docs referenced in my original post are incorrect), and that the way to export/import these records is to:

1. In the source environment, create a new Personal View for the Themes entity with all the columns you want to export
2. In the source environment, go to Dynamics > Advanced Settings > Customization > Themes, select the new Personal View you created, then select the theme record you want to export from the list and click 'Export to CSV'
3. In the target environment, go to Dynamics > Advanced Settings > Customization > Themes, click 'Import Data' and upload the record you exported at 2, above. 
4. Publish the theme

[ChrisPiasecki · Accepted solution]

Hi @cjbarnaby,

You'll need to write some custom scripts to create/update the Theme records via the Dataverse API, and optionally use the PublishThemeRequest to set a specific theme to be the active one. A couple options to do this are:

• Package Deployer - write C# code and use the D365 SDK. 
• PowerShell script - leverage the Microsoft.Xrm.Data.Powershell module which could be run as a deploy task in a DevOps platform such as Github or ADO. 

---
Please click Accept as Solution if my post answered your question. This will help others find solutions to similar questions. If you like my post and/or find it helpful, please consider giving it a Thumbs Up.

[cjbarnaby]

Thanks, @ChrisPiasecki!

I've accepted that as the answer, since it does address the ultimate purpose of the question (despite the subject line of the post being specifically about the Configuration Migration Tool).

[pradeeppednekar]

This is perfectly right, but here there is one challenge that after importing the Theme, we won't be Published as Default.For this we can use the ChrisPiasecki suggested solution to use the PublishThemeRequest method in PackageImportExtension.cs files method of CRM Package Solution:

public override bool AfterPrimaryImport()
{

//Read the Theme Record based on ThemeName and then Use the PublishThemeRequest code to publish
return true;
}

Publish Theme : https://learn.microsoft.com/en-us/dotnet/api/microsoft.crm.sdk.messages.publishthemerequest?view=dyn...

PublishThemeRequest request = new PublishThemeRequest();
request.Target = new EntityReference(Theme.EntityLogicalName, defTheme.Id);//defTheme.Id will be captured from GetTheme Record logic based on Theme Name.
service.Execute(request);

Note : For Data Import do not use the CSV File option,because of Localization this CSV data import may fail.Use the Configuration Migration tool for Data File.