Relations dualpane after upgrade to 2023.06ext6 stopped working

Client
,
1

Hi,

After upgrade to 2023.06-ext6, dualpane with additional fields stopped working.
When I try to add relation, application does not display relationship attributes dialog and it adds empty row.

This is how it looks like now:

broken dual pane
broken dual pane693×384 14.3 KB

This is how it looked like before upgrade:

popup
popup1665×321 16.9 KB

dualpane
dualpane711×402 15.5 KB

Form config:

form config
form config533×528 23.2 KB

2

Dear @m.stepniewski,

We were unable to reproduce this issue you reported on our installer advanced workspace with the Preview App. To assist you better, could you please provide more details and technical information, since this might not be a modelling issue and could be caused by your application settings?

3

Hi, thanks for answer.

What details do you mean?

I checked it on different operating systems and web browsers. Here is my package.json:

package.json (4.9 KB)

4

Hi,

I noticed problem occures not only for relations with addidtional attributes, but also for some of relations without attributes.

Here is my models structure:

I have 4 models A, B, C, D.

Form of model A:

  • Dual Pane for relations A - B - works fine
  • Table List for realtions A - C - works fine
    When I enter the row in table of C elements
    • Dual Pane for relations C - B - does not work
    • Dual Pane for relations C - D (with relation attributes) - does not work
5

Hi,
so as I would understand it you have 4 Relationship models: AB_RM, AC_RM, CB_RM & CD_RM

  • Is that assumption correct?

  • What “Multiplicity” do you use for your corresponding roles in each Relationship-model?

  • If you use a Many-to-Many relationship in your Relationships-models, do you use a Link Document Model Reference?

6

Hi,
thats correct.

AB_RM - many to many
AC_RM - one to many
BC_RM - many to many
DC_RM - many to many with Link Document Model Reference

7

And do you use CDMs in your project?

8

Yes, we do. Problem occures inside of model A CDM-FM.

9

Hello @m.stepniewski,
unfortunately we are unable to reproduce the issue so far. We need to see the set-up of your models more into detail to be able to say if there is a bug or it is a modeling / other type of issue. Could you, please, create a ticket in the A12 Support Portal and share your models with us so that we can analyze the situation more thoroughly?

10

Hi @katerina-icy-token
Thanks for your support. Ticket created.

11

Issue fixed

In principle the issue arises from showing a “not just data”-Regular Form in a ChildActivity. Since the Parent Activity is a CDM, the ChildActivity will also be treated as a CDM and the data handling is taken from the CDM Code. But the Bindings shown in the form are just the “Regular Bindings” (as your form is a regular form) – and hence the data handling does not match
Two supported modeling approaches based on current limitations:

  • CDM based form for “ChildActivity” form + wrapping WoContract-DM in a CDM or reuse “WoContract-CDM-DM”

  • use DetailScreens instead of a ChildActivity for MasterContract-CDM-FM (easiest solution since heterogeneity is not in use)

Consolidation of Regular Relationships and CDM handling planned for October 2024 release. From this point the initial modeling approach described would also work

12

Hi,

Has this ‘consolidation of relationships’ been implemented in latest 2024.06-ext2?