# Modeler: DMN reference lost after BPMN import

**URL:** <https://forum.flowable.org/t/modeler-dmn-reference-lost-after-bpmn-import/8598>\
**Category:** Flowable Engine\
**Created:** [November 3, 2021, 2:52pm UTC](https://forum.flowable.org/t/modeler-dmn-reference-lost-after-bpmn-import/8598 "2021-11-03T14:52:36Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![wberges](https://yyz1.discourse-cdn.com/flex035/user_avatar/forum.flowable.org/wberges/32/940_2.png) [@wberges](https://forum.flowable.org/u/wberges)\
**Post date:** [November 3, 2021, 2:52pm UTC](https://forum.flowable.org/t/modeler-dmn-reference-lost-after-bpmn-import/8598/1 "2021-11-03T14:52:36Z")

</div>

Hello

When I import a BPMN file with a DMN task, the DMN reference is lost.

Process:

- Create a BPMN with a DMN task
- Decision Table reference is set to “_No reference selected_”
- Select an existing DMN as Decision Table reference
- Decision Table reference is set to “_myDMNTable_”
- Save BPMN
- Export BPMN as XML file
- Delete BPMN in modeler
- Import same BPMN as XML file
- Decision Table reference is now set to “_No reference selected_”

I have the same behaviour in Flowable 6.6 & 6.7

Best Regards  
William

---

<div class="post-metadata">

**Author:** ![yvo](https://yyz1.discourse-cdn.com/flex035/user_avatar/forum.flowable.org/yvo/32/2231_2.png) [@yvo](https://forum.flowable.org/u/yvo)\
**Post date:** [November 4, 2021, 2:42pm UTC](https://forum.flowable.org/t/modeler-dmn-reference-lost-after-bpmn-import/8598/2 "2021-11-04T14:42:04Z")

</div>

Hi,

When importing a single BPMN XML the reference is to the DMN decision table (or service) is not set.  
Please use an App export / import for importing models and keeping (and updating when needed) references to other models.

Best Regards,

Yvo

---

<div class="post-metadata">

**Author:** ![wberges](https://yyz1.discourse-cdn.com/flex035/user_avatar/forum.flowable.org/wberges/32/940_2.png) [@wberges](https://forum.flowable.org/u/wberges)\
**Post date:** [November 5, 2021, 7:12am UTC](https://forum.flowable.org/t/modeler-dmn-reference-lost-after-bpmn-import/8598/3 "2021-11-05T07:12:55Z")

</div>

Hi @yvo, thanks for your answer 😁

It means that, without using an App, it is impossible to use and redeploy (manually) only a BPMN without having to set again each time the corresponding DMNs (and Forms?).  
We always have to redeploy the full set of BPMN + DMN + Forms (in the App) just to keep the references in the BPMN?

Thanks again  
Best regards

---

<div class="post-metadata">

**Author:** ![yvo](https://yyz1.discourse-cdn.com/flex035/user_avatar/forum.flowable.org/yvo/32/2231_2.png) [@yvo](https://forum.flowable.org/u/yvo)\
**Post date:** [November 5, 2021, 7:32am UTC](https://forum.flowable.org/t/modeler-dmn-reference-lost-after-bpmn-import/8598/4 "2021-11-05T07:32:44Z")

</div>

Hi,

For forms it’s a bit different. When importing a BPMN XML the static property `formKey` is set.  
But for single BPML XML imports the behaviour for tables / services is as described. (One of the technical reasons is that you don’t have the context of all decision tables available when importing a single BPMN file. This is way you have to do something special in order to determine the `name` and `id` of the referenced decision table; which is needed in the modeler to make the link).  
You could have a look at implementing something like the forms approach and contribute it to the project.

But for now; using apps is the advised way.

Regards,

Yvo

---

<div class="post-metadata">

**Author:** ![wberges](https://yyz1.discourse-cdn.com/flex035/user_avatar/forum.flowable.org/wberges/32/940_2.png) [@wberges](https://forum.flowable.org/u/wberges)\
**Post date:** [November 8, 2021, 1:02pm UTC](https://forum.flowable.org/t/modeler-dmn-reference-lost-after-bpmn-import/8598/5 "2021-11-08T13:02:54Z")

</div>

Ok, thanks for the detailed explanation Yvo 🙂  
Will look for a way to contribute.  
Regards