UX Component -> calculated field based on lookup field value. How to refresh?

[hocomlabs]

So, I have put some time into this problem before writing this question, but I find myself getting farther and farther from home.

I have a UX Component. In that component there is a control with a lookup function that gets a value from a grid. Several fields in the UX are then filled from the corresponding fields in the grid record selected in the lookup.
That all works, and the fields are filled correctly.

Now, the UX's calculated fields are executed on init of the UX component. I know that much. Which means, the calculated field is set to 0 because on init there has not been any record selected in the lookup yet.
Once the record is selected in the lookup, the value of the fields filled changes.
One of those changed fields is used in the calculated field. The latter one does not recompute automatically when the value of one of the used fields in the calculated field changes.

So how do I "refresh" the calculated field?

I have tried to do it with Javascript action scripting on the OnChange event of the used field, but no cigar.

Before I take a really really deep dive into this and spend hours and hours of time, maybe one of you guys can point me into the right direction on how to solve this? Hopefully.

So, example:

(1) Lookup: "choose your package". It provides records of packages available in a grid by means of a lookup.

Shown:
Record 1:
Name: package A
Price: $10

Record 2:
Name: package B
Price: $20

(2) UX Controls:

(a) UX Control: "Chosen Package" -> value inserted from lookup
(b) UX Control: "Price p/package" -> value inserted from lookup
(c) UX Control: quantity -> input from user
(d) UX calculated field: COST (quantity * Price p/package)

Problem: on selecting the package in the lookup field, (a), (b) get filled in correctly. (d) is still 0.
Once the quantity (c) is entered by the user, (d) does not recompute and remains 0.

How to recompute / refresh (d) ??

Any help on this is highly appreciated.

[peteconway]

It's not your fault - but whole thing is what we call in Australia - all over the place like a dogs breakfast - you have 22 posts - so it's time to stop you in your tracks from continuing down the path your heading.
Just say what it is as a specification you are wanting to do and i'll put you on the right track. What is it you want to build.

Pete

[hocomlabs]

It's not your fault - but whole thing is what we call in Australia - all over the place like a dogs breakfast - you have 22 posts - so it's time to stop you in your tracks from continuing down the path your heading.
Just say what it is as a specification you are wanting to do and i'll put you on the right track. What is it you want to build.

Pete

Hi Pete, thank you for offering to help out !

I don't quite "get" your post and the mentioning of my 22 posts , but all I really want to do is offer the user a screen where he can make a choice, enter some data and then have some calculated fields recalculate based upon all of that.
It really (i.m.h.o.) shouldn't be that hard as I encounter it to be. I just want some calculated fields on the UX component to re-calculate based upon the data available AT THAT TIME. Which, I dare to say, should be quite basic a wish?

If I understand correctly, the UX component is the dialog component designed to just do that?
So, if you have a calculated field on the UX, how do YOU re-calculate it when the user enters some data?

Or am I incorrect at a design level, and should I use the component differently to obtain my goal, or even use a different component all together?

Confused.

[TheDevilIsMe]

So, I have put some time into this problem before writing this question, but I find myself getting farther and farther from home.

I have a UX Component. In that component there is a control with a lookup function that gets a value from a grid. Several fields in the UX are then filled from the corresponding fields in the grid record selected in the lookup.
That all works, and the fields are filled correctly.

Now, the UX's calculated fields are executed on init of the UX component. I know that much. Which means, the calculated field is set to 0 because on init there has not been any record selected in the lookup yet.
Once the record is selected in the lookup, the value of the fields filled changes.
One of those changed fields is used in the calculated field. The latter one does not recompute automatically when the value of one of the used fields in the calculated field changes.

So how do I "refresh" the calculated field?

I have tried to do it with Javascript action scripting on the OnChange event of the used field, but no cigar.

Before I take a really really deep dive into this and spend hours and hours of time, maybe one of you guys can point me into the right direction on how to solve this? Hopefully.

So, example:

(1) Lookup: "choose your package". It provides records of packages available in a grid by means of a lookup.

Shown:
Record 1:
Name: package A
Price: $10

Record 2:
Name: package B
Price: $20

(2) UX Controls:

(a) UX Control: "Chosen Package" -> value inserted from lookup
(b) UX Control: "Price p/package" -> value inserted from lookup
(c) UX Control: quantity -> input from user
(d) UX calculated field: COST (quantity * Price p/package)

Problem: on selecting the package in the lookup field, (a), (b) get filled in correctly. (d) is still 0.
Once the quantity (c) is entered by the user, (d) does not recompute and remains 0.

How to recompute / refresh (d) ??

Any help on this is highly appreciated.

I think your missing something with your calculated field , if I get your question right , what you need to do here is changing the way of calculating field , I mean instead of writing the calculated field as

(quantity * Price p/package)

try this

If(cost !="0", (quantity * Price p/package) , 0) // this should be changed upon your needs , try to play with it till you get exactly what you want to do.
Or
if(yourCalculatedField != "0" , The True Result , The False Result ) // think about it this way

notice that your fields have to be numeric type .

I honestly not sure if I got this right formula , but you will need to do it through if condition . that will directly refresh the calculated field .

Let me know if this didn't work for you .

[peteconway]

I'll take a look tomorrow for you as well, The process looks way to complicated - It's late here - Have to get some sleep been at it all day.

Pete

[hocomlabs]

Hi TheDevillsMe !
Thanks for offering your approach. I appreciate your efforts to help me out hugely.

But, I have found the solution just now a few moments ago, experimenting with the possibilities.
And, with hindsight, the solution was quite simple.

On the OnChange Event of the customers entry field on the UX, I placed an inline-Javascript action, holding the following code:

{dialog.Object}.refreshClientSideComputations();

So, the dialog.Object is on run exchanged with the objectid, and all clientside computations will be refreshed, which resulted in the desired behavior of the calculated fields re-calculating!
It was that simple.....

Thanks to everybody reaching out to help!

[gianfior85]

On the OnChange Event of the customers entry field on the UX, I placed an inline-Javascript action, holding the following code:

{dialog.Object}.refreshClientSideComputations();

I have found recently in the newer builds that clientside computations don't run as automatic as they used to in many contexts, especially if your data is being displayed in a 'label' control vs a 'textbox', and have had to use the same command myself when previously I did not.

[madtowng]

I would think onchange event rules for the quantity and package controls would solve the problem.
Each control would check the other control for valid data before populating the price control.
The rules should also blank out the price control if either package or quantity does not have a valid value.