Enable button based on one field being dirty

[dfricke10]

I want to enable a submit button based on certain fields being dirty. Not the entire dialog.

Normally I would use the default of 'dialog.isDirty = true'.

UX component.
Want to enable button if certain fields are dirty.

I'm sure this is easier than I am overthinking it.

[dfricke10]

Re: Enable button based on one field being dirty

Let's say the fields are:

field1
field2
field3

I have a button that I want to be enabled if only 'field1' and 'field2' are dirty. Not 'field3'.

[Davidk]

Re: Enable button based on one field being dirty

Not sure if this is the best way... but...

Get a pointer to the controls you need to be dirty and then get the attribute value for a5isdirty.

var fName = {dialog.Object}.getPointer('FIRSTNAME');
var lName = {dialog.Object}.getPointer('LASTNAME');

var fnDirty = fName.attributes['a5isdirty'].value;
var lnDirty = lName.attributes['a5isdirty'].value;

if(fnDirty=='true' && lnDirty=='true'){
	alert('all we need are Dirty');
}else{
	alert('not everything we need is Dirty');
}

[GGandhi]

Re: Enable button based on one field being dirty

i am not sure this is right way to do
but you could add this in the enable expression

field1 != "" and field2 !=""

that will check if there is any value entered in those fields.

[dfricke10]

Re: Enable button based on one field being dirty

Thanks, gandhi, but I need to check if it's dirty, not if there's a value in it.

[dfricke10]

Re: Enable button based on one field being dirty

Ideally, I'm looking for what to enter in the Enable Expression on the button.

[Davidk]

Re: Enable button based on one field being dirty

This isn't working out the way I thought it might. Here's a bit of a brute force approach... but I'm not happy with it.

Create a TextBox named testDirty and set it's client-side show/hide expression to 1=0.

Create this function...

function testDirtyFields(){

	debugger;
	
	var fName = {dialog.Object}.getPointer('FIRSTNAME');
	var lName = {dialog.Object}.getPointer('LASTNAME');
	
	
	if(fName.attributes['a5isdirty']!= undefined){
		var fnDirty = fName.attributes['a5isdirty'].value;
	}else{
		var fnDirty = false;
	}	
	
	if(lName.attributes['a5isdirty']!= undefined){
		var lnDirty = lName.attributes['a5isdirty'].value;
	}else{
		var lnDirty = false;
	}	
	
	if(fnDirty=='true' && lnDirty=='true'){
		{dialog.Object}.setValue('testDirty','1');
	}else{
		{dialog.Object}.setValue('testDirty','0');
	}

}

And then your Button Enable expression is testDirty=1

Add this to the onChange event of the Fields you want to test... testDirtyFields();

Each time your fields change, the function fires and checks all the fields.

Overall, not pretty. I'm sure there's a more elegant method for doing this.

[dfricke10]

Re: Enable button based on one field being dirty

It would be nice to have a

isDirty = true

type of thing.

Here's my scenario. Customer information. There's numerous tabs, numerous list controls, misc fields from a table, and a search section. All loaded together. You select a record from a list control and open with a container window. So essentially everything is contained in one UX. Can't use the typical dialog.isDirty = true because there's too much on the UX that's dirty from the getgo. Each tab has it's own 'Save' button so I want to make each tab's button not enabled unless someone changes some text in those specific fields.

Here's a visual to kinda help. It's the 'SAVE AND STAY' buttons that I want to have NOT enabled unless some data is changed. Right now they're always enabled. Figured having them not enabled would help the user to know if it's saved.

Screen Shot 2016-12-17 at 5.25.33 PM.png

[Davidk]

Re: Enable button based on one field being dirty

What would be nice is a field1.isDirty AND field2.isDirty as an Enable expression on a button. But I don't think isDirty is available at a control level. The code I've posted will test several fields and set a test field value... which the button enable expression is based on. Closest I can get it... but it works nicely.

[dfricke10]

Re: Enable button based on one field being dirty

Yeah. That's what I meant.

[dfricke10]

Re: Enable button based on one field being dirty

I figured out using your testDirty field with the enable expression on the button, but instead of the Javascript, put

{dialog.Object}.setValue("testDirty","1");

in the onKeyPress event instead of onChange to set the value of the testDirty field. onChange waits until you exit the field to make the change. onKeyPress fires as soon as you type something in the field. And this way I don't have to modify the javascript each time I add a field.

Correct me if I'm wrong on something please, though.

[Davidk]

Re: Enable button based on one field being dirty

Yup... always pick the event that best suits you. But... you get an enabled button per field now. If you're looking for an 'or' process... all good. If you're looking for an 'and' process, you won't have it.

[dfricke10]

Re: Enable button based on one field being dirty

Yes, i want enabled if any field is dirty, not all. Got it working great. Thanks!

[Davidk]

Re: Enable button based on one field being dirty

Yeah... that would have been much easier. I thought you wanted field1 and field2 but not field3. Both field1 AND field2 had to be dirty, but you didn't want to check field3. Anyway... glad it's working... and still good to know about a5isdirty.

[GGandhi]

Re: Enable button based on one field being dirty

instead of checking to see if the a5isdirty custom property of the control why not just change testDirty control value to 1 on the keyPress event, like
{dialog.object}.setValue('TESTDIRTY',1)
this can be on any number of fields and any one changes then it is still dirty.

if you run your dialog in chrome and watch the change, a5isdirty field does change but the dialogwatch function cannot watch that property since it is not a system property. in order to do you have to do what david has done. but you really don't need that much javascript code to do that, in my humble opinion. if find a way to create a system variable i will pass that along.
in any case, glad you found the solution.