From b1ca2a2e4e3b26cd08b0b3cac41303ba41ac4131 Mon Sep 17 00:00:00 2001
From: beatle01 <b.m.m.tel@gmail.com>
Date: Mon, 23 Aug 2021 16:11:03 +0200
Subject: [PATCH] Update MetadataSelector.groovy

When configuring dynamic attributes on the import mapper, the code stores the dynamic attribute without the "+" sign which Cuba requires to distinguish between built-in and dynamic properties. By including the "+" in the select options (and thereby saving it as such) this problem is avoided.
---
 .../cuba/dataimport/web/util/MetadataSelector.groovy          | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/modules/web/src/de/diedavids/cuba/dataimport/web/util/MetadataSelector.groovy b/modules/web/src/de/diedavids/cuba/dataimport/web/util/MetadataSelector.groovy
index 5757f55..180bd98 100644
--- a/modules/web/src/de/diedavids/cuba/dataimport/web/util/MetadataSelector.groovy
+++ b/modules/web/src/de/diedavids/cuba/dataimport/web/util/MetadataSelector.groovy
@@ -55,7 +55,7 @@ class MetadataSelector {
         Collection<CategoryAttribute> dynamicAttributesForImportConfiguration = dynamicAttributes.getAttributesForMetaClass(entityMetaClass)
 
         dynamicAttributesForImportConfiguration.collectEntries {
-            ["${it.name} (${it.code})".toString(), it.name]
+            ["${it.name} (${it.code})".toString(), "+"+it.name]
         }
     }
     Map<String, Object> getDirectAttributesLookupFieldOptions(MetaClass entityMetaClass) {
@@ -100,4 +100,4 @@ class MetadataSelector {
         metadata.tools
     }
 
-}
\ No newline at end of file
+}