«BeginGroup:ASSE»
Name: «Text:NAME»
Desc: «Text:DESC»
Type desc: «Text:TYPE_DESC»
«EndGroup:ASSE»
«BeginGroup:DIDX»
Name: «Text:NAME»
Extension: «Text:EXT»
«EndGroup:DIDX»
|
«BeginGroup:PRIG»
Name:
«Text:NAME»
Desc:
«Text:DESC»
Note:
«Text:NOTE»
«EndGroup:PRIG»
Name:
AAA
Desc:
«Text:DESC»
<- Should beDesc: as column is present in DataTable, value null
Note:
«Text:NOTE»
Name:
BBB
Desc:
«Text:DESC»
<- Should beDesc: as column is present in DataTable, value is "" (string.Empty )
Note:
«Text:NOTE»
Name:
CCC
Desc:
ccc
Note:
«Text:NOTE»
If the replacement for null or string.Empty will be fixed, maybe the need to have real WMergeFields instead names can be cancelled: our need to have WMergeField instance was to have the chance,if a mergefield is not replaced, to understand its belonging group to inform the user properly, but checking management better we found out that maybe it's not necessary as each mergefield in a group in case of multiple rows in related DataTable is "duplicated" for each row, so if we read the document before any management and collect all mergefield to use later for checks -> after replace of a group, the starting mergefield is no longer present as it's "cloned" for each row.... so the check we want to perform is not possible. We can check mergefield names belonging to a group versus DataTable column names to advice user.
I've sent our helper class in a private mail.