Simple UX question for client side calculated fields

[jrodder]

Hello all you good people of AA! I will preface this with I am *not* a JS developer, and my knowledge of AA is limited. I have an app that is using a calculated field that currently works when testing for one condition, but I am getting hung on on trying to test multiples.

if(MTA_Placement = "Unsafisfactory - Location",5,0)

So the 'score' field looks to the MTA_Placement field (dropDownBox with static text values). I need to test for multiple possible text values and evaluate for that to set the score #. I have tried many many things and don't know if it's a syntax issue or I need to be attacking it in a different way. Any input is greatly appreciated!

-Jared

[lvasic]

Re: Simple UX question for client side calculated fields

I would call a javascript function and use a "Switch Statement" to evaluate it.

[Stan Mathews]

Re: Simple UX question for client side calculated fields

That looks like a simple xbasic expression. You can nest if() statements but case() is often easier to maintain by adding logical test and return value pairs.

case(MTA_Placement = "Unsafisfactory - Location",5,MTA_Placement = "OK",99,.T.,0)

[lvasic]

Re: Simple UX question for client side calculated fields

Here's a no code way to make it work. https://www.screencast.com/t/jds6I69J

[lvasic]

Re: Simple UX question for client side calculated fields

Here's the same solution with a little javascript: https://www.screencast.com/t/xNhwHFPz

[CharlesParker]

Re: Simple UX question for client side calculated fields

might be interesting if you showed the really fancy method details! I liked the record count part.

[jrodder]

Re: Simple UX question for client side calculated fields

Very very cool. As always, it looks like I was stuck inside a box of thinking, instead of trying to see a completely alternative way to solve the problem. I really appreciate the screencasts, I will take a harder look and try to get that working. Thanks so much for your time, Ivasic!

-Jared

[jrodder]

Re: Simple UX question for client side calculated fields

That looks like a simple xbasic expression. You can nest if() statements but case() is often easier to maintain by adding logical test and return value pairs.

case(MTA_Placement = "Unsafisfactory - Location",5,MTA_Placement = "OK",99,.T.,0)

Another reason I suppose I need to look at xbasic a bit more. Javascript solutions are just easier to find out there in search engine land. :)

[lvasic]

Re: Simple UX question for client side calculated fields

This one is for Charles:

https://www.screencast.com/t/f0MyHRt9c3

Most of this excellent code came from DavidK.

var emailArray = []; 
var lObj = {dialog.Object}.getControl('SPlay'); //targeting list control

	for(i=0;i<lObj.selectionData.length;i++){
		emailArray.push(lObj.selectionData[i].Plays);
 	}
      
   	var emailStr = emailArray.join(',\n');
   	emailStr = emailStr + '\n' +'_______________________';
    emailStr = emailStr + '\n' + 'Total Plays: ' + lObj.selectionData.length;
	{dialog.object}.setValue('ListOfChoices',emailStr);

[peteconway]

Re: Simple UX question for client side calculated fields

Nice

[CharlesParker]

Re: Simple UX question for client side calculated fields

Hey - thank you, Lee! I finally had time to look at this, in fact, I almost forgot but luckily I didn't! I have to ask though, are you just reusing code or are you about to email out a list here? It is fast as lightning!

[iRadiate]

Re: Simple UX question for client side calculated fields

That's awesome! I don't think I've ever seen a list used that way, very cool.

Thanks Lee (and David).