Field value not set via dependency (CDM context)

Modeling
1

Dear modeling experts,

I have a problem with dependencies, computations and CDMs and I’m not entirely sure if we discussed such a case before, but I couldn’t find it here. So here it goes:

I have:

  • an enumeration called Selection in modelA-DM
  • a boolean called Applicable in modelA-DM
  • a computation that calculates the Applicablefield in a CDM that combines modelA with others
  • a dependent field dependency on Selection with Applicable as trigger
    image
    image662×324 14.2 KB

The computation works correctly and hiding the Selection enumeration works perfectly.
Setting the value of Selection to false doesn’t work, though.

I have an almost exact same case, with the only difference that the computation of the Applicable boolean is not in the CDM but in the same model as the fields. And in that case hiding and setting a value works.

Any insight is appreciated! Since the workaround I have in mind is very painfull :frowning:

Cheers
Bianca

2

Hi @bianca-firm-knoll

I’ve created some test models in 2023.06-ext8 and…

I’ve got a question relating to your statement,

When does this not work?

In my test models, the boolean Applicable was initially set to false. This lead to the Selection control being hidden but the value was not set to false as:

  • No initial value was set for Selection
  • The value of Applicablehad not changed from something else to false

In my test models, once the value of Applicablehad not changed from something else to false, the value of Selectionwas set correctly.

If you need Selection to be set initially to false, have you tried modeling and Initial Value for the Control?

3

Sorry, I forgot to actually explain my bug case.
Here it is:

  • You need a computation that computes Applicable
  • You need to change fields that trigger the computation and turn Applicable = true
  • Then Selection is visible and pre-filled with false
  • Change Selection to true manually
  • Then change the fields that trigger the computation and turn Applicable = false
  • Then Selection is hidden, but its value remains true but should be set to false

In my case the computation that computes Applicable is in a CDM and not in the model where all other fields were modeled. I have a case with the same logic and setup, where the computation is in the same model as all other fields. In that case it works. Although that doesn’t make much sens to me, since the computation works fine. Applicable is correctly set to false and Selection is correctly hidden. Only setting its value to false is not working…

I hope that helps you to investigate my problem further :pray:

Thanks a lot!
Bianca

4

So I’ve set up my models as you described and I cannot reproduce your issue.

I’ve sent you my 2023.06-ext8 models privately so that I can share the whole workspace with you. In these models:

  1. Selection is pre-filled with the Initial Value false
  2. The Computation Rule for Applicable means that this field is also initially false
  3. As a result, Selection = false and hidden
  4. Adding a linked document and checking the checkbox updates the computation of Applicable to true
  5. As a result Selection = false and visible
  6. I can manually change the value of Selection
  7. Adding, deleting or changing the data in the linked Document updates Applicable to false
  8. As a result, Selection = false and hidden and I can see this in the overview after saving the document.
5

After investigating this with @bianca-firm-knoll we found that this Value Dependency does not work when the linked Documents are changed (without changing any values on those Documents).

If the linked Documents are edited so that the same Documents have different Values, then the Dependency is triggered as expected.

As a result, we created a bug ticket, A12-16505

6

Hello @bianca-firm-knoll, the corresponding Bug ticket was done for the 2024.06-ext3 release. Therefore, after migration the problem should be solved.