setValue not really working

[gamma]

Re: setValue not really working

Good Morning Selwyn,

that makes sense. I should have known or at least tried something else out. I am learning something new each day and that is actually really fun. The textbox works for me just as well.
So thanks a million for your help!

[Selwyn Rabins]

Re: setValue not really working

Based on this thread, we have decided to make the following change to .getValue() when it is used on a Label.

This will be in the next update:


Dialog .getValue() on a Label Control - Would always return the original value of the label (even if the label's value had been previously changed using the .setValue() method. This is now fixed so that .getValue() will always read the label value from the control itself.

The reason that .getValue() previously worked they way it did was that, generically, the .getValue() method returns the control value from the .originalValues[] array in the Dialog Object if the control is NOT dirty, but reads the control value from the control itself if the control is dirty. When you use .setValue() on a Label, the control does NOT go dirty (because a Label control has no concept of being 'dirty' since it is not an input control).

[gamma]

Re: setValue not really working

Thank you for the update!

[gamma]

Re: setValue not really working

Hi Selwyn,

I have another question concerning your post #9.
After clicking on the submit button I process the insert and updates in the server side Event "afterDialogValidate". I want that after the event is finished all data now is in e.oldDataSubmitted. so when the user enters some more data and clicks submit again I only find the fields dirty the user changed since the first submit.
I tried adding

{dialog.object}.refreshClientSideComputations();

in the client side event "afterValidate" but that did not help. In

e.repeatingSectionInfo["CONTAINER_1"].dirtyFieldsInSection

I always find all fields dirty the user has changed since the first time he opend the Window. is there anything similar to "{dialog.object}.refreshClientSideComputations();" I can use in XBASIC in the afterDialogValidate Server side event in order to achieve the same thing?
Thank you!!

Hi Selwyn,

do you by any chance have an anser to my issue in The post #12 (quote above)?
Thank you very very very much!

[Selwyn Rabins]

Re: setValue not really working

What I think you are asking is how to set the Dialog state in the afterValidate event so that the NEXT time it is submitted, the values from the PREVIOUS submission are in the e.oldDataSubmitted object.
If that is indeed your question, then this video might help you understand more about the issue.


http://www.ajaxvideotutorials.com/V1...idateEvent.swf

I am also not sure what you were hoping to achieve by calling the .refreshClientSideComputations() method. This method simply causes the client side calculations (calc fields, show/hide expression, enable expressions, summary value calculations) to be recomputed. It would have no bearing on set dirty fields, or initial field values.

[gamma]

Re: setValue not really working

Thank you Selwyn! That was exactly what I was looking for!
Your videos always are great!

I have another issue with populating the repeating section.
So the first time a user opens the dialog the Repeating Section has a defined amount of rows , let's say 8. When he clicks the back button the number of rows can change and with it the data of the repeating Section.

So when the dialog is initialized Following JavaScript code is executed:

{dialog.Object}._setRepeatingSectionRowCount('CONTAINER_1', 8,true,false);
var _d= {};
_d['project:1'] = 12;
$('{dialog.componentName}.V.R1.PROJECT_A5INSTANCE1').title = '12';
_d['project:2'] = 23;
$('{dialog.componentName}.V.R1.PROJECT_A5INSTANCE2').title = '23';
_d['project:3'] = 31;
$('{dialog.componentName}.V.R1.PROJECT_A5INSTANCE3').title = '31';
_d['project:4'] = 26;
$('{dialog.componentName}.V.R1.PROJECT_A5INSTANCE4').title = '26';
_d['project:5'] = 27;
$('{dialog.componentName}.V.R1.PROJECT_A5INSTANCE5').title = '27';
_d['project:6'] = 29;
$('{dialog.componentName}.V.R1.PROJECT_A5INSTANCE6').title = '29'';
_d['project:7'] = 30;
$('{dialog.componentName}.V.R1.PROJECT_A5INSTANCE7').title = '30';
_d['project:8'] = 28;
$('{dialog.componentName}.V.R1.PROJECT_A5INSTANCE8').title = '28';
  {dialog.object}.populate(_d);
  {dialog.object}.prepare();

The first column (project) populates correctly. So the user clicks the back button the following code is fired

{dialog.Object}._setRepeatingSectionRowCount('CONTAINER_1', 10,true,false);
var _d= {};
_d['project:1'] = 12;
$('{dialog.componentName}.V.R1.PROJECT_A5INSTANCE1').title = '12';
_d['project:2'] = 23;
$('{dialog.componentName}.V.R1.PROJECT_A5INSTANCE2').title = '23';
_d['project:3'] = 31;
$('{dialog.componentName}.V.R1.PROJECT_A5INSTANCE3').title = '31';
_d['project:4'] = 24;
$('{dialog.componentName}.V.R1.PROJECT_A5INSTANCE4').title = '24';
_d['project:5'] = 25;
$('{dialog.componentName}.V.R1.PROJECT_A5INSTANCE5').title = '25';
_d['project:6'] = 26;
$('{dialog.componentName}.V.R1.PROJECT_A5INSTANCE6').title = '26';
_d['project:7'] = 27;
$('{dialog.componentName}.V.R1.PROJECT_A5INSTANCE7').title = '27';
_d['project:8'] = 29;
$('{dialog.componentName}.V.R1.PROJECT_A5INSTANCE8').title = '29';
_d['project:9'] = 30;
$('{dialog.componentName}.V.R1.PROJECT_A5INSTANCE9').title = '30';
_d['project:10'] = 28;
$('{dialog.componentName}.V.R1.PROJECT_A5INSTANCE10').title = '28';
  {dialog.object}.populate(_d);
  {dialog.object}.prepare();

In the beginning I had this column as a dropdown Box in order to give it the Id and let it show the corresponding text instead. So I thought that might be the problem and changed it to a textbox in order to see the IDs. Here is what I see:
A5_populateProjectRS.jpg

It seems like any position/row containing already a value, does not change and just the tow new Rows are populated correctly. The titles/tooltips on the other hand work as intended. In this case the tooltip shows the correct value but the textbox does not. What did I do wrong here?
The second code block is generated by an Ajax Callback.
Thanks again!

[Selwyn Rabins]

Re: setValue not really working

it is really difficult (actually impossible for me) to answer a question like this without having a test component that demonstrates the issue.
if i have a test component i can run it, duplicate the issue, and suggest a solution.

thanks.

[gamma]

Re: setValue not really working

Hi Selwyn,

of course your right. So I created a test component, as you are missing the database backend, and it worked. It took me a while to figure out why. It had to be something in my original component that was not in the test component, that was causing the problem. And I just found it. It was an error on my side. I was missing a variable declaration in JS

	var _d = {};

So the populate method called afterwards did no longer do what I wanted.
Sorry about the confusion, but my current save issues do lead to loss of code.

So thank you for your help. From now on I will always build a test component if I have a problem and if that does not work then I will ask.
Have good start into the new week!

[Steve Wood]

Re: setValue not really working

Sorry if I hitch hike on this related thread, but I need the Dialog2 equivalent to these two Grid functions:

{grid.object}._setDetailViewState(true);
{grid.object}._setRowState(1,true);

I need to use an external js command to set the Dialog2 dirty (enable the Submit button) without setting values on the form. But I want it to start out with the Submit button disabled as normal. My method works for the Grid using the two functions above.

[Selwyn Rabins]

Re: setValue not really working

the submit button on a dialog is just a standard button that comes with a pre-defined client-side enable expression. if you want the button to be enabled regardless of the dialog state then just remove the client side enable expression.

if you don't want to do that then just set some control to a new value and then set it back to its original value.

e.g.

var x = {dialog.object).getValue('FIELD1');
{dialog.object}.setValue('FIELD1','JUNK');
{dialog.object}.setValue('FIELD1',x);

[Steve Wood]

Re: setValue not really working

Thank you. I will add a dummy filed to the dialog and use method 2.

[Selwyn Rabins]

Re: setValue not really working

of course, you could hide the dummy field so that it is not visible.