Skip to main content

Notifications

Announcements

No record found.

News and Announcements icon
Dynamics 365 Community / Forums / Dynamics 365 general forum / Unmanaged Solution Imp...
Dynamics 365 general forum

Unmanaged Solution Import Failure

(0) ShareShare
ReportReport
Posted on by David Wood

Hi Everyone

Hoping someone can help me out here, having made only one change to an un-managed solution (creating a new relationship) I now am stuck with a solution that wont import in to my test environment and returns the bellow error:

The element 'Workflow' has invalid child element 'ProcessTriggers'. List of possible elements expected: 'XamlFileName, ImageFileName, Type, Subprocess, Category, Mode, LanguageCode, Scope, OnDemand, TriggerOnUpdateAttributeList, TriggerOnCreate, TriggerOnDelete, AsyncAutodelete, SyncWorkflowLogOnFailure, StateCode, StatusCode, CreateStage, UpdateStage, DeleteStage, Rank, processorder, processroleassignment, RunAs, SdkMessageId, UniqueName, IsTransacted, IntroducedVersion, IsCustomizable, RendererObjectTypeCode, BusinessProcessType, FormId, PrimaryEntity'.

0285A6ACD.xaml</XamlFileName><Type>1</Type><Subprocess>0</Subprocess><Category>0</Category><Mode>1</Mode><Scope>4</Scope><OnDemand>0</OnDemand><TriggerOnUpdateAttributeList>activestageid,statecode</TriggerOnUpdateAttributeList><TriggerOnCreate>0</TriggerOnCreate><TriggerOnDelete>0</TriggerOnDelete><AsyncAutodelete>0</AsyncAutodelete><SyncWorkflowLogOnFailure>1</SyncWorkflowLogOnFailure><StateCode>1</StateCode><StatusCode>2</StatusCode><UpdateStage>20</UpdateStage><RunAs>0</RunAs><IsTransacted>1</IsTransacted><IntroducedVersion>1.0.0.0</IntroducedVersion><IsCustomizable>1</IsCustomizable><PrimaryEntity>tsg_nmcoppprocess</PrimaryEntity><LocalizedNames><LocalizedName languagecode="1033" description="NMC Opp Process - Create Stage Timing Record" /></LocalizedNames></Workflow><Workflow WorkflowId="{919e14d1-6489-4852-abd0-a63a6ecaac5d}" Name="Lead to Opportunity Sales Process" Description="This is the default process flow to work on a lead and convert it to an opportunity." unmodified="1"><ProcessTriggers /></Workflow><Workflow WorkflowId="{24026e27-359c-4f1f-a040-ab9a721c6112}" Name="Account - Set OOTB County"><XamlFileName>/Workflows/Account-SetOOTBCounty-24026E27-359C-4F1F-A040-AB9A721C6112.xaml</XamlFileName><Type>1</Type><Subprocess>0</Subprocess><Category>0</Category><Mode>0</Mode><Scope>4</Scope><OnDemand>0</OnDemand><TriggerOnUpdateAttributeList>tsg_county</TriggerOnUpdateAttributeList><TriggerOnCreate>1</TriggerOnCreate><TriggerOnDelete>0</TriggerOnDelete><AsyncAutodelete>1</AsyncAutodelete><SyncWorkflowLogOnFailure>0</SyncWorkflowLogOnFailure><StateCode>1</StateCode><StatusCode>2</StatusCode><RunAs>1</RunAs><IsTransacted>1</IsTransacted><IntroducedVersion>1.0.0.4</IntroducedVersion><IsCustomizable>1</IsCustomizable><PrimaryEntity>Account</PrimaryEntity><LocalizedNames><LocalizedName languagecode="1033" description="Account - Set OOTB County" /></LocalizedNames></Workflow><Workflow WorkflowId="{30b8a3b1-7f96-48f0-87bc-b3a32c2b3370}" Name="Contact - Set Conesnt E

All of the workflows referred to in the error where present prior to the solution failing to import and none of them have been modified.

Any help with this would be much appreciated.

  • Manuel Steiner Profile Picture
    Manuel Steiner 192 on at
    RE: Unmanaged Solution Import Failure

    I had a service request open with Microsoft they sdaid it'll be fixed this weekend with version 9.0.2.1718 and today I checked and it was updated and now I can import the solution again.

  • Community Member Profile Picture
    Community Member Microsoft Employee on at
    RE: Unmanaged Solution Import Failure

    I have a service request open with Microsoft on this same issue.  They have acknowledged it is a bug on their side.

    This is the latest I heard from them on 09/07/2018...

    >> We have an update from our internal team that, the bug fix will be updated all over the world for North America region in Online Version 9.0.2.1718. As of Now our Online Version is 9.0.2.1470, this update will happen in your Non-Business hours i.e. on this weekend thus it will not impact your productivity.

  • Ashly Lee Gonzalez Gonzalez Profile Picture
    Ashly Lee Gonzalez ... 10 on at
    RE: Unmanaged Solution Import Failure

    Hi,

    I've been facing the exact issue, has anyone been able to make it work?

    Thanks,

    Ash

  • gvrijdag Profile Picture
    gvrijdag 45 on at
    RE: Undamaged Solution Import Failure

    Hi Everyone!

    Any news yet from Microsoft regarding the error when importing a solution? Does anybody know of any formal confirmation of the error? If so, please share a link to it.

    Just isolating workflow seems not to be sufficient as business rules are effecting the process as well and therefore the import of entities…

    Best regards,

    Guido Vrijdag

  • Shweta_Shukla Profile Picture
    Shweta_Shukla 105 on at
    RE: Undamaged Solution Import Failure

    Hi David,

    try adding the <PrimaryEntity> tag right before your <ProcessTriggers> tag starts. You have to add the primary entity schema name in your <PrimaryEntity> tag, like, in your case it would be <PrimaryEntity>opportunity</PrimaryEntity>

  • Henrik H Profile Picture
    Henrik H 90 on at
    RE: Undamaged Solution Import Failure

    I forgot to write that I got the same error (The element 'Workflow' has incomplete content) after replacing the ProcessTriggers-tags with empty strings. In my case this was because of a default BPF which has not been customized at all, which was still part of my solution:

        <Workflow WorkflowId="{0ffbcde4-61c1-4355-aa89-aa1d7b2b8792}" Name="Phone to Case Process" Description="This is the default process flow for working on a case." unmodified="1">
      <ProcessTriggers />
    </Workflow>

    You should be able to read the text from the error to see what it is complaining about. After removing the ProcessTriggers-tag, we end up with the following:

        <Workflow WorkflowId="{0ffbcde4-61c1-4355-aa89-aa1d7b2b8792}" Name="Phone to Case Process" Description="This is the default process flow for working on a case." unmodified="1">
    </Workflow>


    The above is apparently not valid either, and results in The element 'Workflow' has incomplete content. It worked for me to simply remove the entire workflow from the XML (or alternatively removing it from the solution).

  • Suggested answer
    Ben Thompson Profile Picture
    Ben Thompson 6,350 on at
    RE: Undamaged Solution Import Failure

    There is supposedly an import issue in the release that was made last week. A patch is supposedly in the works and will be out sometime this week.

  • David Wood Profile Picture
    David Wood on at
    RE: Undamaged Solution Import Failure

    That seems to have just moved things on to a new error:

    "The element 'Workflow' has incomplete content. List of possible elements expected: 'XamlFileName, ImageFileName, Type, Subprocess, Category, Mode, LanguageCode, Scope, OnDemand, TriggerOnUpdateAttributeList, TriggerOnCreate, TriggerOnDelete, AsyncAutodelete, SyncWorkflowLogOnFailure, StateCode, StatusCode, CreateStage, UpdateStage, DeleteStage, Rank, processorder, processroleassignment, RunAs, SdkMessageId, UniqueName, IsTransacted, IntroducedVersion, IsCustomizable, RendererObjectTypeCode, BusinessProcessType, FormId, PrimaryEntity'."

    Again comparing to a previously working solution file nothing appears to have changed.

  • Suggested answer
    Henrik H Profile Picture
    Henrik H 90 on at
    RE: Undamaged Solution Import Failure

    I have experienced the same issue. Both my source and target environments are version 1710 (9.0.2.1468). By looking at the XML, I can see that the exported solution contains self-closing ProcessTrigger tags in all BPFs without any triggered processes.

    <Workflow [...]>

    [...]

    <ProcessTriggers />

</Workflow>

    By comparing the XML that is currently exported from D365 with previously exported XML I can see that there have been no changes. Previously self-closing ProcessTrigger tags were also exported, so the exported XML appears to be unchanged.

    It seems that Microsoft has changed (and broken) the validation of the XML when running an import. A fix is to either:

    • Through the UI actually add a triggered process to all BPFs that currently do not have one (e.g. a process that does nothing).
    • Or: Edit the customizations.xml before importing where you search+replace <ProcessTriggers /> with an empty string.

    I recommend using the latter solution until Microsoft fixes the issue. I have not contacted support about this, but if someone does, please update this thread.

  • David Wood Profile Picture
    David Wood on at
    RE: Undamaged Solution Import Failure

    Nope, the error is even occurring when trying to import the solution in to a new instance

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

November Spotlight Star - Khushbu Rajvi

Congratulations to a top community star!

Forum Structure Changes Coming on 11/8!

In our never-ending quest to help the Dynamics 365 Community members get answers faster …

Dynamics 365 Community Platform update – Oct 28

Welcome to the next edition of the Community Platform Update. This is a status …

Leaderboard

#1
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 291,280 Super User 2024 Season 2

#2
Martin Dráb Profile Picture

Martin Dráb 230,235 Most Valuable Professional

#3
nmaenpaa Profile Picture

nmaenpaa 101,156

Leaderboard

Featured topics

Product updates

Dynamics 365 release plans