-
New Commercial Services Section
We have now opened a commercial services section here on the forum for registered users. If you have a Fabrik project that you wish to have someone work on for you, post it under Help Wanted. If you are an application developer and wish to earn some money helping others, post your details under Fabrik Application Developers.
Both of these are unmoderated. It will be up to both parties to work out the details and come to an agreement.
-
Joomla 5.1
For running J!5.1 you must https://fabrikar.com/forums/index.php?wiki/update-from-github/ or include the new file manually https://fabrikar.com/forums/index.php?threads/joomla-5-1-and-fabrik-cannot-find-files-error.54473/post-285151 See also Announcements
Wrong sum in calc element
- Thread starter verzevoul
- Start date
rob
Administrator
What setting do you have in the calc element for 'Only Calc on Save' - if its set to no then the calculation value is not necessarily stored in the database and thus our sum code can't work out the correct value (as its run via an sql SUM() query on the recorded data.
So I would check that all db records contain a value for the calc element
So I would check that all db records contain a value for the calc element
cheesegrits
Support Gopher
Just to correct Rob ...
The calc result is always stored in the database, on save.
"Calc on save ONLY" set to Yes means we will use that saved value when displaying the value, for instance when displaying Lists. This avoids the overhead of re-calculating the value for every row in the list.
Setting it to No means we will ignore the stored value, and re-calc it when displaying the value.
Which setting you use depends on the nature of your calc, and if it involves variables which are outside of the "scope" of the row it is on, i.e. you can't guarantee it should have the same result when displayed, as when the form was last saved.
For instance, if it involves looking up value(s) in other table(s), which may have been changed independently of "this" table / row, then you would need to set this to No, and re-calc the value every time it is displayed.
Whereas if the calc is something simple, like joining 'first_name' and 'last_name' into 'full_name', and you know the first and last name elements on that form will never be changed except by submitting the same form, you can set it to Yes, and only ever calc it when saving the form.
-- hugh
The calc result is always stored in the database, on save.
"Calc on save ONLY" set to Yes means we will use that saved value when displaying the value, for instance when displaying Lists. This avoids the overhead of re-calculating the value for every row in the list.
Setting it to No means we will ignore the stored value, and re-calc it when displaying the value.
Which setting you use depends on the nature of your calc, and if it involves variables which are outside of the "scope" of the row it is on, i.e. you can't guarantee it should have the same result when displayed, as when the form was last saved.
For instance, if it involves looking up value(s) in other table(s), which may have been changed independently of "this" table / row, then you would need to set this to No, and re-calc the value every time it is displayed.
Whereas if the calc is something simple, like joining 'first_name' and 'last_name' into 'full_name', and you know the first and last name elements on that form will never be changed except by submitting the same form, you can set it to Yes, and only ever calc it when saving the form.
-- hugh