I am afraid that here we shift in conceptual point of views.
The detail you added shows a table (the one I used and that is a tipical concept of DBMS) that should bheave like a sheet (that is a tipical concepts of spreadsheets software).
While spreadsheets easly refer data as-you-see and have primitives able to handle the previous-next concept or allow you to refer data by-cell, DBMS can have a likewise functionality implementing indexes. So the prev-next record is non necessary the prev-next record you see displayed but the one according the index you are referring to....
Speaking SQL, we can obtain the result you want in this way:
SELECT index_key,
order_nu,
order_date,
order_item,
dollar_value,
sum ( dollar_value ) over ( order by index_key rows unbounded preceding ) sum_of_dollar_value
FROM Test_ordes;
but I am afraid this is not possible to use in CASPIO.
The workaround you could use is to add one more colum to the table that make the index of your table
The change the task in this way:
When you run it you get:
ATTENTION: I think this is not a solution. It can be used as workaround if you consider:
Values are not updated in realtime when you add a record, but only after the task runs
We do not know what is the limits or constrains that could be arise when the table has a lot of records (perfomance? timeout?)
The first to SET statements is the only way I found to initialize the variable. If you omit the first one the variable is instantiated as an integer and all decimals are lost
The For statement cannot be done on the table, but on the SELECT result because you need to consider the ORDER BY
The WHERE specification is needed otherwise you get the result of the last sum on all records.....
I say again low-code bring an encapsulation of the below infrastructure and some capabilities you have using it directly are hided.
UPDATE
@ParkLoey I think that if you make available a Directory structure is very belittled if it is "just for Caspio app use". This for two reasnons: the first is that a Directory is very useful if it can be work like and identity provider for other system; the second is that CASPIO cannot undervaluate the potential of Wordpress used as front-end. Tons of functions easy to implement with wordpress are very far to be implemented with CASPIO.
ANYWAY I FOUND THE SOLUTIONS and is quite simple. From Wordpress you need to set the logout URL redirection to the CASPIO URL logout. In this way when users logout they quit the session with Wordpress and then also the CASPIO one.
The only contraindication is the miniorange plugin price. You can have this functionality with the Free one too, but at login your users will be redirected to the wordpress dashboard. This could be undesired.
vidierre's post in Create a task to update a table field with the running total (aka sum) was marked as the answer