ConfiForms Edit control - dialog mode shows different ConfiForms field definition from TableView

[Alice Liu]

Hi @Alex Medved _ConfiForms_ and ConfiForms Team,

We use ConfiForms to build an internal expense tracking system, and encounter issue that the expense total calculated and display in TableView is different from the "dialog mode" rendered from Edit Control (TableView number is corrent but rendering in Edit Control is wrong). As internal data is sensitive, I use an abstract example as below to express the issue.

In the system we use TableView and Edit control - Edit record button for a summary list, and for expense calculation we use ConfiForms rules for field definition like below:

ConfiForm Field: Total

Rule for definition:

- field name: Field1, Field2, Field3

- Action to execute: Set expression

- Value to set: Total = [entry.Field1]+[entry.Field2]+[entry,Field3]

And the summary list use TableView, ConfirForms Field and Edit control as attachment.

The total number in TableView would be different from in the dialog window in Edit Control, but the ConfiForm Field is the same. In TableView it is correct, and don't know why in Edit control rendering it becomes a large number which we also don't know how it came up. Sanpshots are as below attachment.

I had checked the documents but there were little info on this rendering mechanism, so really need your help to see how we can fix this.

Thank you!

Attachment:

TableView, ConfiForm Field and Edit control structure:

number in TableView and in Edit Control is different. In TableView it is correct, and don't know why in Edit control rendering it becomes a large number which we also don't know how it came up.

[Alex Medved _ConfiForms_]

Most probably your rule is set to run on form load and not only on user action - which makes it run for 3 times, as it is set to be on 3 fields.

You can enable debug mode for the ConfiForms FormView Registrations Control macro to see which rules gets triggered and in what order. But I believe that setting the rule to trigger on user action only (parameter in the ConfiForms Field Definition Rules macro) will fix the problem