Hi,

The live data update checkbox is already on, so the problem is usually that this page is not connected to that object's updates, or the way the process writes the value doesn't send a refresh. Since it works on your other pages, compare MyApplication against a working page on each point below.

1. Is MyApplication a Freedom UI page?

Live data update only works on Freedom UI pages. If MyApplication is a Classic UI page, or the section opens the record in a classic page, the checkbox does nothing. Then you either rebuild the page in Freedom UI or add code to refresh it (a client message plus a page reload).
Check: open the page in the designer. A Freedom UI page uses the drag-and-drop designer with components on the left.

2. Is the checkbox on the right object?

The setting only matters on the object that is the page's primary data source. Common mismatches:

• The page is based on a different object, such as a replacement or a similarly named object (for example UsrMyApplication versus UsrApplication).
• Field ABC belongs to a related object (for example Contact.ABC shown through a lookup), and the process updates that related record. Then the related object needs live data update enabled too.
• The process updates a different object from the one the page is showing.

Check: in the page designer, look at the data source and its object name. Compare it with the object in the process's Modify data element.

3. Was the object saved and published after you ticked the box?

Ticking the box is not enough. You need to Save and Publish the object. Then log out and back in, or clear the browser cache, so the page loads the new setting.

4. How does the process write ABC?

• Modify data element: sends the update to open pages. ✅

• Script task that writes with direct SQL (Update, CustomQuery, a raw UPDATE ...): skips the object layer, so no update is sent to the page. ❌

  If you need a script, save through an Entity instead, for example entity.SetColumnValue(...) followed by entity.Save().

5. Signal timing

If the signal fires on Record modified and the user saves from the same page, the process can write ABC while the page is still finishing its own save. The page then keeps the old value it has in memory.

• In the signal element, make sure "Run following elements in background" is ticked so the calculation runs after the save completes.
• If the user still has unsaved changes on the page, the incoming value may not overwrite the form. Test with a clean, saved record.

6. Is ABC a real field on the page?

ABC must be bound to the object's column through the page's data source. If it is a page attribute or a custom field filled by a handler, live update won't refresh it.

The first thing to check is publishing and compiling the object, then performing the test after compilation is complete.

Quick test to narrow it down: open a MyApplication record in one browser tab. In another tab, open the same record in the section list, or as a different user, and change ABC by hand.

• If the first tab doesn't update, the cause is points 1 to 3 (page or object setup).
• If it does update but the process change doesn't show, the cause is points 4 or 5 (how or when the process writes the value).

Hi,

You can do this in a business process with no code. Process formulas in Creatio are compiled as C# expressions, so you can use Math.Pow inside a formula field even though the formula editor has no "power" button.

Process layout

[Signal: record added / modified (fields P, B, n)]
        ↓
[Read data: the record]
        ↓
[Formula: i]  →  [Formula: Pow]  →  [Formula: A]
        ↓
[Modify data: set field A]

1. Start signal

• Use an Object signal on your object, triggered by "Record added" or "Record modified".
• For "modified", tick only the fields P, B, n. If you leave A ticked, writing A starts the process again and it loops.
• You can use a button on the page that runs the process instead.

2. Read data

Read the record by Id = Signal.Unique record Id.

3. Process parameters

Add three Decimal parameters: i, Pow, Result. Fill each one with a Formula element:

i

[#Read data.First item of resulting collection.B#] / 100m / 12m

Write 100m / 12m (decimal literals). If B is an Integer field, B / 100 does integer division and gives 0.

Pow = (1 + i)ⁿ

Convert.ToDecimal(Math.Pow(Convert.ToDouble(1 + [#i#]), Convert.ToDouble([#Read data.First item of resulting collection.n#])))

Math.Pow works with double and Creatio fields are decimal, so the formula converts to double and back.

Result = A

[#i#] == 0 
  ? [#Read data.First item of resulting collection.P#] / [#Read data.First item of resulting collection.n#]
  : Math.Round([#Read data.First item of resulting collection.P#] * [#i#] * [#Pow#] / ([#Pow#] - 1), 2)

The i == 0 branch covers a 0% rate (B = 0). Without it the formula divides by zero, because the payment is then just P / n.

4. Modify data

Update the same record (Id = Signal.Unique record Id) and set A = [#Result#].

Notes

• One formula is possible. You can put the whole calculation into one formula inside Modify data, but three separate parameters are much easier to debug: you can see each value in the process log.
• Check the result. With P = 10 000, B = 12, n = 12, you should get A ≈ 888.49.
• Live value on the page. The process runs after the record is saved, so A appears only after save and refresh. If you need A to update while the user types, a business process won't do that; you'd need a page handler, which means code.

Oleg Drobina,

Thank you Oleg, appreciate it for the feedback