Skip to main content

Notifications

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Dynamics 365 general forum / Failed Solution Import...
Dynamics 365 general forum

Failed Solution Import: The element 'Workflow' has invalid child element 'ProcessTriggers'

(0) ShareShare
ReportReport
Posted on by dansiemens

Hello all.

Made some trivial changes to our Sandbox install (calculated field, added a new view), exported and then attempted to import the .zip into our Production install. On doing so I get the error "The element 'Workflow' has invalid child element 'ProcessTriggers'". Upon digging further into the xml, it looks like this is being caused by one of our Business Process Flows that has been running perfectly fine for multiple versions. I tried importing an older solution into Production (which had previously successfully imported), and I got the same error.

At no point have I edited the xml, so it seems odd that this isn't properly validating anymore - especially on previously versions that were successfully imported. Any suggestions?

  • Henrik H Profile Picture
    Henrik H 90 on at
    RE: Failed Solution Import: The element 'Workflow' has invalid child element 'ProcessTriggers'

    @Kjeld: Both your suggestions should be viable. See the following answer: community.dynamics.com/.../838889

  • Kjeld Poulsen Profile Picture
    Kjeld Poulsen 180 on at
    RE: Failed Solution Import: The element 'Workflow' has invalid child element 'ProcessTriggers'

    I am having the same problem, but I am not sure i understand the suggested solution.

    Do i have to edit the XML before importing, or can i do something with the businessworkflow causing the problem, and then create a new solution that will import correctly. ?

  • Verified answer
    dansiemens Profile Picture
    dansiemens on at
    RE: Failed Solution Import: The element 'Workflow' has invalid child element 'ProcessTriggers'

    It looks like the problem was being caused by a deactivated managed Business Process Flow that was created by the System. It's xml contains "<ProcessTriggers />", which is the source of the problem; deleting it from the xml seems to solve the import issue. However there seems to be no way to remove it from our solution since it is a System component. Therefore the best solution is to simply add a triggered Workflow to one of the steps, but keeping the overall Business Process deactivated. That way the xml will output the proper <ProcessTriggers>...</ProcessTriggers> tags, and the solution will properly validate.

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... 292,492 Super User 2025 Season 1

#2
Martin Dráb Profile Picture

Martin Dráb 231,305 Most Valuable Professional

#3
nmaenpaa Profile Picture

nmaenpaa 101,156

Leaderboard

Featured topics

Product updates

Dynamics 365 release plans