Dynamics Community Forum Thread Details

Hi there,

I am facing serious issues trying to export a solution that includes Cloud Flows.

I am doing this on a full copy of our development environment that I just copied recently to a newly created environment. The environment was successfully copied, Dynamics itself also runs smoothly. I moved it out of the administration mode, added a new solution, added a new Cloud Flow, added a Dataverse trigger and a compose action to the Flow. Minimal solution - only one Cloud Flow, nothing else added to the solution.

Whenever I try to export the solution, I get the following error:

Workflow export: FAILURE, workflow id {fad08b79-ad06-ec11-94ef-00224884d75a} category ModernFlow name ExportTest

I find this error not really helpful - so I am trying to get more details by using the old interface.

Trying to run the solution checker fails - "could not complete solution check".

When using the old interface (via Dynamics itself, not the PowerApps interface), I get a more detailed error message:

Exception type: System.ServiceModel.FaultException`1[Microsoft.Xrm.Sdk.OrganizationServiceFault]
Message: Workflow export: FAILURE, workflow id {fad08b79-ad06-ec11-94ef-00224884d75a} category ModernFlow name ExportTestDetail: 

  705db43c-2e2e-4e9a-92e3-7ea7a3d44b1a
  -2147220970
  
    
      ApiExceptionSourceKey
      Plugin/Microsoft.Crm.WebServices.ExportXmlService
    
    
      ApiSourceActivityKey
      Microsoft.Crm.Extensibility.PipelineStep
    
    
      ApiExceptionOwnerKey
      COMMONDATASERVICECDS\CDSAPI-Reliability
    
    
      ApiOriginalExceptionKey
      Microsoft.Crm.CrmException: Workflow export: FAILURE, workflow id {fad08b79-ad06-ec11-94ef-00224884d75a} category ModernFlow name ExportTest ---> Microsoft.Crm.CrmException: Workflow export: FAILURE, workflow id {fad08b79-ad06-ec11-94ef-00224884d75a} category ModernFlow name ExportTest ---> System.ArgumentNullException: Value cannot be null.
Parameter name: key
   at System.ThrowHelper.ThrowArgumentNullException(ExceptionArgument argument)
   at System.Collections.Generic.Dictionary`2.Insert(TKey key, TValue value, Boolean add)
   at Microsoft.Crm.ObjectModel.ConnectorDataProvider.GetAllCustomConnectorDictionaryWithSelectedFields[T](ExecutionContext context, String keyFieldName, String valueFieldName, Boolean caseSensitiveKeys)
   at Microsoft.Crm.ObjectModel.ConnectorDataProvider.GetAllCustomConnectorDictionaryWithSelectedFieldByApiHubId[T](ExecutionContext context, String valueFieldName)
   at Microsoft.Crm.Tools.ImportExportPublish.WorkflowHandler.GetModernWorkflowJsonFileContent(WorkflowEntity workflow)
   at Microsoft.Crm.Tools.ImportExportPublish.WorkflowHandler.ExportModernWorkflowJsonFile(WorkflowEntity workflow, XmlNode node, XmlDocument document)
   at Microsoft.Crm.Tools.ImportExportPublish.WorkflowHandler.ExportAllItems(XmlDocument xDoc, XmlNode node, WorkflowEntity workflow)
   at Microsoft.Crm.Tools.ImportExportPublish.WorkflowHandler.ExportItem(XmlDocument xDoc, XmlNode node)
   --- End of inner exception stack trace ---
   at Microsoft.Crm.Tools.ImportExportPublish.WorkflowHandler.ExportItem(XmlDocument xDoc, XmlNode node)
   at Microsoft.Crm.Tools.ImportExportPublish.ExportHandler.Export(XmlDocument xDoc)
   at Microsoft.Crm.Tools.ImportExportPublish.RootExportHandler.RunExport()
   at Microsoft.Crm.WebServices.ExportXmlService.ExportSolutionInternal(String solutionName, Boolean managed, String targetVersion, Boolean exportAutoNumberingSettings, Boolean exportCalendarSettings, Boolean exportCustomizationSettings, Boolean exportEmailTrackingSettings, Boolean exportGeneralSettings, Boolean exportMarketingSettings, Boolean exportOutlookSynchronizationSettings, Boolean exportRelationshipRoles, Boolean exportIsvConfig, Boolean exportSales, Boolean exportExternalApplications, ExecutionContext context)
   at Microsoft.Crm.WebServices.ExportXmlService.ExportSolutionWithTargetVersion(String solutionName, Boolean managed, String targetVersion, Boolean exportAutoNumberingSettings, Boolean exportCalendarSettings, Boolean exportCustomizationSettings, Boolean exportEmailTrackingSettings, Boolean exportGeneralSettings, Boolean exportMarketingSettings, Boolean exportOutlookSynchronizationSettings, Boolean exportRelationshipRoles, Boolean exportIsvConfig, Boolean exportSales, Boolean exportExternalApplications, ExecutionContext context, ExportComponentsParams exportComponentsParams)
   --- End of inner exception stack trace ---
   at Microsoft.Crm.Extensibility.VersionedPluginProxyStepBase.Execute(PipelineExecutionContext context)
   at Microsoft.Crm.Extensibility.PipelineInstrumentationHelper.Execute(Boolean instrumentationEnabled, String stopwatchName, ExecuteWithInstrumentation action, PipelineExecutionContext context)
   at Microsoft.Crm.Extensibility.Pipeline.<>c__DisplayClass3_0.b__0()
    
    
      ApiStepKey
      681f0f11-8e01-40a1-8d84-424242bb392c
    
    
      ApiDepthKey
      1
    
    
      ApiActivityIdKey
      705db43c-2e2e-4e9a-92e3-7ea7a3d44b1a
    
    
      ApiPluginSolutionNameKey
      System
    
    
      ApiStepSolutionNameKey
      System
    
    
      ApiExceptionCategory
      SystemFailure
    
    
      ApiExceptionMessageName
      UnExpected
    
    
      ApiExceptionHttpStatusCode
      400
    
  
  http://go.microsoft.com/fwlink/?LinkID=398563&error=Microsoft.Crm.CrmException:80040216&client=platform
  Workflow export: FAILURE, workflow id {fad08b79-ad06-ec11-94ef-00224884d75a} category ModernFlow name ExportTest
  2021-08-26T20:39:55.6300752Z
  false

Can anyone point me towards where this error could be coming from?

Is there anything I missed copying my dev environment to a new environment?

This is a real problem, as I can't export the solution that I have built.

Best,

FlowwithoutW

Here's the answer from Microsoft on this topic from beginning of October 2021:

This is an unexpected behavior when the copy is done from another organization.

It was confirmed by our product team. We will need to do the following mitigation to resolve the issue.

Source organization will be XXXX

Targe environment: YYYY

In source environment, move custom connectors to a separate solution if the solution you are having trouble exporting in the target env also has connection references.

Export the custom connector solution, and the solution with the connection references and flows in source environment.

In target env, import the custom connector only solution first.

In target env, import the solution with the connection references and flows after the custom connector import succeeds.

You should now be able to add back your custom connectors to the original solution and be able to export.

Note this only works if you have unmanaged solutions in the source. If you have managed solutions, create a unmanaged solutions and use "add existing" to add your components and then export.

Similarly, you can only combine the components into one solution if its unmanaged.

So this problem is confirmed - there is a workaround that involves moving some of the components. I haven't tried this workaround myself, so I can't let you know whether it really works.